primordic/IssueDupesLite huggingface dataset:
Repository: freedomofpress/securedrop

Issue #3643: Remove 3.14.79 kernels from securedrop-grsec metapackage
Created: 2018-07-16T21:24:07Z
Description
securedrop-grsec metapackage still pulls in 3.14.79-grsec kernel packages. We should remove these kernels from the dependencies.
https://github.com/freedomofpress/securedrop/blob/develop/install_files/ansible-base/group_vars/all/securedrop#L56
User Stories
As an admin, I don't want to have old and unnecessary packages on my system
As an admin, I don't want installs to take a long time when downloading dependencies

Duplicate issue #3148: Remove old 3.14.79 grsec kernel
Created: 2018-03-13T16:56:07Z
Description
In SecureDrop 0.6, in #3142 we added the old grsec 3.14.79 kernel package as a dependency to the securedrop-grsec metapackage to ensure that they would not be removed from instances that needed the old kernel as a fallback.
We should remove the 3.14.79 grsec kernel in a future version of the metapackage once any/all compatibility issues are resolved.
User Stories
As a SecureDrop admin, I want unnecessary packages to be removed from my system.

Closing comment (2018-07-16T21:28:24Z): Closing this one in favor of duplicate #3643 for visibility ;-)
Repository: freedomofpress/securedrop

Issue #749: Verify contents of prod-specific.yml before installing SecureDrop
Created: 2014-11-16T00:09:57Z
When installing SecureDrop, the admin is asked to fill out prod-specific.yml before running an ansible-playbook command which installs the software and configures/hardens the servers. As part of the installation process, the ansible-playbook command should verify the contents of prod-specific.yml before continuing.
That is, we need to make sure the information we require for the install is present in the file, and we also need to make sure the information that is present is accurate. The installation process does not seem to complain about the fact that the IP address I entered for the Monitor Server is "192.168.1.522".

Duplicate issue #1257: GPG keys should be validated against fingerprints before provisioning
Created: 2016-03-08T21:59:50Z
The application will fail if the GPG key fingerprint is wrong.
Related: #1252

Closing comment (2016-04-28T23:51:30Z): @heartsucker wrote an implementation to address this problem in #1259. Rather than use a bash script, let's try the more tedious—but idempotent—approach in pure Ansible tasks.
Other improvements to the "validate" role are tracked in:

#749
#858
#1029
Repository: freedomofpress/securedrop

Issue #1357: Make HTML/CSS responsive
Created: 2016-07-06T10:23:30Z
Currently many of the elements have fixed sizes (in pixels). This led to some ugly and poorly sized containers for the German translations in #1103 because of long words. It would probably look equally bad with very short words as in Chinese.
Before piling on more features, it might make sense to refactor the HTML/CSS (or hopefully SASS #1349) to support containers that resize depending on content size (as well as possibly monitor size). As I'm not usually a frontend dev, I'd roll it all by hand and skip a framework.
Currently there are a lot of features that require front changes, so it would be good to make this change before starting any of the others:  #1356, #1355, #1354, #1353,  #1171, #1170, (plus a nasty rebase of #1103)

Duplicate issue #1600: SI is very large and doesn't scale properly
Created: 2017-03-02T02:40:19Z
On my 1920x1200 external monitor I must scroll horizontally to view the whole page. I heard from @Hainish it is possible to get the viewport size without JS (although TBB may and hopefully does employ additional protections against this). If this is unfortunately possible, we may as well take advantage of it to scale the SI. If it isn't we should at least try to have it render okay on the most popular (tiny by my standards) screen size, 1366x768 [1].
[1] https://techcrunch.com/2012/04/11/move-over-1024x768-the-most-popular-screen-resolution-on-the-web-is-now-1366x768/

Closing comment (2017-09-22T05:32:23Z): Making the HTML/CSS responsive for both interfaces solves this, tracked in #1357
Repository: froala/wysiwyg-editor

Issue #2807: Make the new paragraph "escape" the formatting of the previous paragraph
Created: 2018-05-14T12:05:48Z
Expected behavior.
When pressing Enter a new paragraph is created. I want the paragraph to be clean (with no formatting kept from the previous paragraph).
Actual behavior.
If the previous paragraph is bolded the newly created paragraph will also be bolded. It's the same with underline, italic, font-color and so on.
Does an option exist to make the new paragraph "escape" the formatting of the previous paragraph?
Thank you!

Duplicate issue #2963: Make the new paragraph "escape" the formatting of the previous paragraph
Created: 2018-07-16T14:58:06Z
Expected behavior.
When pressing Enter a new paragraph is created. I want the paragraph to be clean (with no formatting kept from the previous paragraph).
Actual behavior.
If the previous paragraph is bolded the newly created paragraph will also be bolded. It's the same with underline, italic, font-color and so on.
Does an option exist to make the new paragraph "escape" the formatting of the previous paragraph?
Thank you!
#2807

Closing comment (2018-07-16T16:26:03Z): Closing this as a duplicate of #2807.
Repository: froala/wysiwyg-editor

Issue #737: Sticky toolbar is misplaced when editor is moved in the DOM
Created: 2015-09-09T15:55:22Z
I am creating a content editor which uses the Froala editor for rich text blocks. The user can rearrange the blocks of content but after the blocks have been moved, the editor miscalculates where the sticky toolbar should be (it uses the position of the editor before it was moved).
The moving in my case is handled by Angular (although I don't believe the issue is specific to Angular, but rather an issue with extracting a section of the DOM tree containing the editor and reinserting it at another point).
I can't see any method for the editor that I could call for it to perform a reinitialization of the sticky toolbar since I think this will be something to do manually at the point of DOM mutation. Without using a mutation observer in the editor code I think something like this is necessary for those wanting to move the editor around.

Duplicate issue #814: Toolbar jumps when other textarea is resized
Created: 2015-10-02T12:29:07Z
If I have "stickyToolbar: true" and another textarea above Froala and resizes the textarea, then Froala's toolbar will stick to the top of the other textarea when i scroll.
The problem is in Chrome, Edge, IE and not in Firefox (haven't tried Safari).
Here is a CodePen that shows the problem.
Steps to reproduce:

resize the height of the textarea
scroll down
see that the toolbar will stick to the top textarea

Closing comment (2015-10-05T10:19:24Z): Related to #737 (comment).
Repository: froala/wysiwyg-editor

Issue #672: Table cell highlight is incorrect at times
Created: 2015-08-31T11:30:11Z
As seen on picture below - sometimes when dealing with tables with merge cells, blue highlight is wrong, no to mention at times there's some "ghosting" - blue highlight is partly there for previously highlighted cells (it goes away after moving mouse around). Ubuntu, Chrome 44, editor on https://www.froala.com/wysiwyg-editor/v2.0 page.

Duplicate issue #765: Highlight table only on two sides
Created: 2015-09-18T08:34:38Z
Table highlighting highlights all four sides of the cell when the cursor is in the cell, but when you leave the cell will it look like the picture below.

Windows 10
Chrome 45

Closing comment (2015-09-23T14:07:37Z): Duplicate of #672.
Repository: froala/wysiwyg-editor

Issue #1572: Wrong toolbar position with multiline text
Created: 2016-10-19T08:56:50Z
Expected behavior.
The toolbar position should appear above the selected text (as usual)
Actual behavior.
The toolbar position is wrong. In this case it is centered.
Steps to reproduce the problem.

https://jsfiddle.net/124c4cqp/13/
Write some multi line text (breaklines)
Select Text
See toolbar position


OS.
OSX El Capitan v 10.11.2
Browser.
Google Chrome Version 53.0.2785.143 (64-bit)

Duplicate issue #1742: Inline Froala Menu - Centres itself when empty <p>'s are added
Created: 2017-02-06T15:22:32Z
Expected behavior.
When highlighting copy that has a double paragraph (e.g. p  br  p ) the inline editor should ignore the width of the empty p
Actual behavior.
When highlighting copy that has a double paragraph the inline editor takes into consideration the width of the empty p tag causing it's position to be way off.
Steps to reproduce the problem.
Use inline WYSIWYG editor type and press enter twice then type again. Now highlight the copy.
Video: https://cl.ly/3B0W0536153H
OS.
Windows 10
Browser.
Chrome

Closing comment (2017-02-09T09:13:45Z): Duplicate of #1572 (comment).
Repository: froala/wysiwyg-editor

Issue #4398: Editor scrolls to top when text color/background applied
Created: 2022-01-31T21:23:40Z
Expected behavior.
Using the menu bar to set the color or background of text should keep the scroll position
Actual behavior.
Editor scrolls to top of document which is extremely confusing for the user
Steps to reproduce the problem.

Open this fiddle: https://jsfiddle.net/grassick/tf79a3g0/5/
Scroll down to "HERE"
Set its color to green
See that editor scrolled to top, confusing and frustrating the user!

Editor version.
4.0.8
OS.
Linux Mint 19.3
Browser.
Chrome Version 97.0.4692.99

Duplicate issue #4408: Editor scrolls to top when image alignment is changed
Created: 2022-02-15T13:15:18Z
Expected behavior.
Using the image popover to change image alignment should keep the scroll position
Actual behavior.
Using the image popover to change image alignment scrolls to the top of document which is extremely confusing for the user
Steps to reproduce the problem.

Add some content to the editor, so it can scroll
Add an image to the end of content
Change the image alignment
See that editor scrolled to the top, confusing and frustrating the user

Editor version.
4.0.9
4.08
4.0.7
OS.
Mac OS
Browser.
Chrome 97.0.4692.99
Recording.

Closing comment (2022-02-15T13:17:00Z): Probably related to #4398
Repository: froala/wysiwyg-editor

Issue #1246: Froala editor becomes unresponsive when selecting table cells
Created: 2016-05-10T07:27:09Z
Expected behavior.
Froala editor remains responsive while selecting table cells
Actual behavior.
Froala editor becomes unresponsive - toolbar greyed out, no toolbar buttons work, can't enter or edit text.
Steps to reproduce the problem.

Create a Froala editor with visible/sticky toolbar with a table in it and some text outside the table - I used the example found on the main page of the Froala site here https://www.froala.com/wysiwyg-editor and added a table.
Click and drag across multiple table cells to select them but don't release the cursor until you're back over the Froala toolbar.
The cells appear highlighted, but the editor toolbar is now completely unresponsive, and clicking on text or inside a table cell to edit text doesn't work - editor appears stuck in limbo/unresponsive (maybe awaiting completion of the table cell select, but not registering the release on the toolbar?).
Can 'snap' the editor back out of this state by click-dragging across table cells again, but this time making sure to release over a cell. Unfortunately, our users freaked out and abandoned the page, meaning they lost content they were editing.

OS.
Mac OS X 10.10.5
Browser.
Google Chrome Version 50.0.2661.86 (64-bit)
Safari v9.1

Duplicate issue #2256: Editor becomes unresponsive when cells selection involves text.
Created: 2017-10-16T12:10:54Z
Expected behavior.
Invalid selections should leave the editor active.
Actual behavior.
When multi-cells selection includes pure text (defined inside or outside of the table) the editor becomes unresponsive (controls are disabled).
Steps to reproduce the problem.
I've been able to reproduce this bug sporadically without having to go outside of the table or press ⌘-A but due to its randomness here are the steps that constantly allowed me to reproduce it.
In Froala Editor:

insert a table with at least 2 cells
insert some text below table
start selecting cells in the table
without releasing the click, go outside of the table over the text and press ⌘-A.
editor becomes unresponsive (controls are disabled).

OS.
macOS Sierra - 10.12.6
Browser.
Chrome Version 61.0.3163.100

Closing comment (2017-10-16T12:48:16Z): Seems to be a related to #1246
Repository: froala/wysiwyg-editor

Issue #2004: If parent div has overflow-x property, inline style attribute is not removed after fullscreen mode
Created: 2017-05-29T12:02:34Z
Expected behavior.
When entering fullscreen mode, Froala puts an inline style attribute on the parent div style="z-index: 9990; overflow: visible;"
After returning from fullscreen mode the style attribute on the parent div is removed, also when the parent div has an overflow-x CSS-property.
Actual behavior.
When returning from fullscreen mode the parent div still has a style="overflow: visible;" which overrides the overflow properties for the div set in the CSS file.
Steps to reproduce the problem.
Codepen showing the issue:
https://codepen.io/eblax/pen/dWELwW

Use Froala editor 2.6.0 or newer - the issue does not seem to occur in version 2.5.1 and older.
Put the froala editor in a parent div.
Give the parent div the CSS properties

overflow: auto;
overflow-x: hidden;


Go to fullscreen mode.
Go back.
See that the parent div now has an inline style="overflow: visible;"

OS.
Windows 10
Browser.
Problem reproduced in latest versions of Chrome and Firefox. Does not seem to be an issue on Edge.

Duplicate issue #2005: inline style overflow:visible on parents is not removed when exiting fullscreen
Created: 2017-05-30T10:23:57Z
Expected behavior.
inline added style should be removed when exiting fullscreen
Actual behavior.
z-index is removed but not overflow visible
Steps to reproduce the problem.
Make a parent between body and editor with overflow:auto & overflow-x:hidden by default. It's the only parent that keep the inline overflow:hidden when exiting fullscreen
OS.
Windows 10
Browser.
Chrome Canary (and only canary, so the bug is not real until some release)

Closing comment (2017-07-19T14:46:56Z): @stefanneculai we still have the issue on 2.6.2, so it appears it was not the same as #2004. We will try to make a codepen of fiddle asap. Could you re-open this issue meanwhile?
Repository: froala/wysiwyg-editor

Issue #1401: Uncaught TypeError: Cannot read property 'get' of undefined
Created: 2016-07-12T15:52:39Z
Expected behavior.
Should not throw an exception while cutting/copy.
Actual behavior.
It is showing an Uncaught TypeError: Cannot read property 'get' of undefined error in console whenever text is copied or cut (Win: CTRL+X) from editor.
On Firefox it says TypeError: mt is undefined.
Steps to reproduce the problem.
open this link, keep your devtools (console tab) open and try to copy or cut a text from the demo editor.
OS.
Windows 10, macOS
Browser.
Chrome, Opera, Firefox

Duplicate issue #1402: Throwing exception on copy or cut
Created: 2016-07-12T16:04:22Z
Expected behavior.
It should not throw an exception when copying or cutting from editor.
Actual behavior.
It shows a Uncaught TypeError: Cannot read property 'get' of undefined error in console when trying to copy or cut from editor.
Steps to reproduce the problem.
Visit the link, keep your devtools (console tab) open and try copying or cutting text from demo editor.
On Firefox is says TypeError: mt is undefined.
OS.
Windows 10, macOS
Browser.
Chrome, Opera, Firefox

Closing comment (2016-07-12T16:13:32Z): Duplicate of #1401
Repository: froala/wysiwyg-editor

Issue #2078: url plugin bug(TLD problem)
Created: 2017-07-06T10:11:27Z
Steps to reproduce the problem.
test.jpg
test.exe
Froala Version.
2.6.2
The domain link feature does not work correctly because the regular expression in the plugin does not check Domain TLD.
I changed the code by referring to the regular expression below.
https://autohotkey.com/boards/viewtopic.php?t=15269
  $.FE.URLRegEx = '(^| |\\u00A0)((https?:\\/\\/(www\\.)?)?((?:[-a-zA-Z0-9@:%_\\+~#=]{2,256}\.)?(?:[-a-zA-Z0-9@:%_\\+~#=]{2,256}\.)(com|net|jp|kr|co|`domainTLD`)|([\\d]{1,3}\\.[\\d]{1,3}\\.[\\d]{1,3}\\.[\\d]{1,3}([-a-zA-Z0-9@:%_\\+~#?&/=]*))))$';
Also, it seems better to remove $.FE.KEYCODE.PERIOD from the key event.
Please check. :)

Duplicate issue #2094: unwanted link on strings
Created: 2017-07-17T14:32:21Z
Expected behavior.
only link real links such as www.example.com or mail@example.com
Actual behavior.
links everything with "." in it. for example:
something.pdf   to   https://something.pdf/
some.string       to   https://some.string/
Steps to reproduce the problem.
type string with dot in editor.
Version.
latest 2.6.2
Browser.
Firefox 54.0.1

Closing comment (2017-07-17T16:09:28Z): Duplicate of #2078.
Repository: froala/wysiwyg-editor

Issue #1694: Dropdowns in IE are not going away
Created: 2017-01-12T19:46:54Z
Expected behavior.
When a font size is selected, it applies the changes and dropdown collapses
Actual behavior.
The fontsize dropdown does not go away (see gif)
Steps to reproduce the problem.

OS.
Windows 8/10
Browser.
Internet Explorer (Version 11.0.9600.18500)

Duplicate issue #1611: IE11 - link popup / image popup sometimes hides itself
Created: 2016-11-15T09:07:00Z
Expected behavior.
When clicking INSERT LINK in IE, popup opens.
Actual behavior.
Sometimes popups hide automatically. This happens at least in inline mode - it's really annoying for basic users as this sometimes happens and sometimes not.
Steps to reproduce the problem.
Inline editor, enter paragraphs and select text, INSERT LINK. Video explains better.
OS.
Windows 7
Browser.
IE 11.0.9600.18524
VIDEO: http://synergiafoxy.fi/julkinensiirto/IE_bug.mp4

Closing comment (2017-03-10T22:10:36Z): Unfortunately we cannot find a way to reproduce this. It might be related to #1694, but we couldn't reproduce that either.
Repository: fullcalendar/fullcalendar

Issue #4580: plugin(moment): Module "moment" has no default export.
Created: 2019-03-26T12:22:51Z
Bug Report
Using moment 2.24.0 I get a typescript error:
ERROR in node_modules/@fullcalendar/moment/main.d.ts(2,12): error TS1192: Module '"***/node_modules/moment/moment"' has no default export.

Duplicate issue #4583: wrong import for moment
Created: 2019-03-27T07:39:34Z
I'm working with fullcalendar in Angular 7
Currently the moment module (@fullcalendar/moment) is declared with a deprecated method and cause errors when compile project.
The correct way for moment module is:
declare module "@fullcalendar/moment" {
    import * as moment from "moment";
    import { Calendar, Duration } from "@fullcalendar/core";
    export function toMoment(date: Date, calendar: Calendar): moment.Moment;
    export function toDuration(fcDuration: Duration): moment.Duration;
    const _default_10: import("@fullcalendar/core/plugin-system").PluginDef;
    export default _default_10;
}
The 1st line needs the '* as' in import moment.
Good job otherwise!
Marc

Closing comment (2019-03-27T19:51:44Z): Yes, this is a duplicate of:
#4580
↑
Could you please visit the link, give a 👍  to vote (?), press the 🔈Subscribe button to receive updates?
Repository: fullcalendar/fullcalendar

Issue #2253: Select and move/edit multiple events
Created: 2015-08-19T12:21:21Z
Originally reported on Google Code with ID 1988
User Stories:
- select events across days in a time-slot and move them to a new time-slot and/or
day
- select events across time-slots in a day and move them to a new time-slot and/or
day
- select discontiguous events and move them to different time-slots and/or days

Additional Requirements:
- selections should move as a relative group, for example, selecting and moving events
(mon8am and tue9am) to (thu7am and fri8am), respectively
- visual indicators should suggest where the events will drop
- selections should adhear to the snapping to grid features
- selections should be initiated with the shift-key on drag or the alt-key on click
- selections should not be able to move beyond the visible calendar time-slots and/or
days, for example, - selecting and moving events (mon and tue) to (sat and sun), respectively
is not permitted in a calendar view showing days sun,mon,tue,wed,thu,fri,sat


Reported by doug@onvelocity.com on 2013-09-04 13:29:08
Imported with 13 stars

Duplicate issue #3752: Drag many events at a time [feature request]
Created: 2017-07-20T13:46:25Z
Sorry if this is duplicated, i search in issues and in pull requests but i didnt find anything like.
Feature request
Would be nice if I could select multiple events at once and drag them all. Maybe using the selectable options or control clicking the events

Closing comment (2017-08-09T21:21:55Z): dup of
#2253
↑
Could you please visit the link, give a 👍  to vote (?), press the 🔈Subscribe button to receive updates?
Repository: fullcalendar/fullcalendar

Issue #3783: Calendar's "today" date is not updated
Created: 2017-08-11T05:32:24Z
This is a simple issue so I though of not creating any demo.
If you have the calendar open in week view in an application, and you visit the application the next day, it shows the current date as the day before (or the date you visited application the last time). While the current time marker is somehow at the right place and the actual date.
It makes sense though, as the current time update code runs in an interval function so it will have proper value. It also makes sense that current date (today) is calculated only once and will not update until the view refreshes.
I'm not sure if there can be any fix for this but one solution that may work would be to check current date while updating the current time. And if any change is required then update the current date.
For people facing same issue would be to force update the view which will allow FC to recalculate everything (simple way would be to provide refresh button for users to handle it manually).
Note: I have not tested it out in day/month views. And week view here refers only to agendaWeek view.
My assumption is the problem will stand in all kind of views.

Duplicate issue #3560: Have future "now" date trigger today button enable/disable
Created: 2017-02-28T13:29:58Z
After midnight a new date starts, but the today button in the header is still disabled.
We already call $('#calendar').fullCalendar('refetchEvents'); periodically to get an up-to-date calendar, this doesn't trigger the updateToolbarsTodayButton function (likely because the currentView didn't change).
Would it be possible to always call the updateToolbarsTodayButton function on re-render or expose the function so we could call it in our script?

Closing comment (2020-06-25T15:58:01Z): yes, same as
#3783
↑
Could you please visit the link, give a 👍  to vote (?), press the 🔈Subscribe button to receive updates?
Repository: fullcalendar/fullcalendar

Issue #6457: Events times are cutoff with eventDisplay: "block" when there is not enough space for the title
Created: 2021-07-14T18:12:32Z
Reduced Test Case
https://codepen.io/Gkleinerva/pen/mdmRZKp
You can observe the behavior described below by changing the "eventDisplay" property between "block" and "auto" in the codepen.  The effect is more pronounced on smaller width windows.  The event that I used to demonstrate the issue is on June 12 2021 on that calendar.
Bug Description
Screenshots captured from codepen above
By default "dayGridMonth" displays non-full-day events using "eventDisplay: 'auto'".  In this view, it appears that the time of the event is given precedence over the title of the event when space is limited, which seems like desired behavior:

However, when you use "eventDisplay: 'block'" in dayGridMonth, longer titles readily crowd out the time in the header:

I think block eventDisplay should be updated to prioritize showing the time in the header similar to auto eventDisplay.  It seems more important to fully display the time for each event than to show a few more characters of the title.  Thank you for your hard work and providing this wonderful tool  :)
Misc information
Browser: Chrome version 91.0.4472.124 (Official Build) (64-bit)
OS: Windows
Full Calendar version: https://cdn.jsdelivr.net/npm/fullcalendar@5.8.0/main.min.js
Originally observed using the Angular component

Duplicate issue #6754: Truncate long event title with ellipsis
Created: 2022-03-09T14:22:16Z
PR: #6750
Checklist

 I've already searched through existing tickets
 Other people will find this feature useful

Feature Description
In dayGridMonth view if the event's title is too long, the time gets cut off. It's also not clear that the event title is actually longer than what is currently displayed, and is overflowing:

This change stops the time from being cut off, and shows an ellipsis if the text is about to overflow (the latter is not as important in my opinion).

PR: #6750

Closing comment (2024-10-22T02:17:49Z): Duplicate of #6457 (comment)
I already have a fix in v7-beta
Repository: fullcalendar/fullcalendar

Issue #2758: timeGrid events incorrectly overlapping
Created: 2015-08-19T12:39:45Z
Originally reported on Google Code with ID 2493

I found an unexpected scenario on fullcalendar where events start hiding each other
when many are on the screen. The minimal set I found to reproduce this error is composed
by nothing less than 12 events, and if any of these 12 events is removed or changed,
the bug disappears.

Please take a look on the demo at http://jsbin.com/xizujo/1/edit?js,output (or http://plnkr.co/F2bzehY8Pc9Vo3D4H5Lc)
and search for the events L and B. You will actually not be able to find B because
L is hiding it, so move L far from its position and B is gonna appear. The screenshots
1 and 2 show this process.

Does anybody has any clue what is going on with event B?

Reported by vd@churchdesk.com on 2015-04-28 10:01:28

- _Attachment: 1.png![1.png](https://storage.googleapis.com/google-code-attachments/fullcalendar/issue-2493/comment-0/1.png)_
- _Attachment: 2.png![2.png](https://storage.googleapis.com/google-code-attachments/fullcalendar/issue-2493/comment-0/2.png)_
Imported with 2 stars.

Duplicate issue #3396: Event overlaped with slotEventOverlap set to false
Created: 2016-10-28T10:12:18Z
Sometimes events are overlaped with slotEventOverlap: false option.
Demo: https://jsfiddle.net/b14hkwun/2/

Closing comment (2016-10-30T08:46:38Z): dup of:
#2758
↑
@oscamen, could you please visit the link, give a 👍  to vote (?), press the 🔈Subscribe button to receive updates?
Repository: fullcalendar/fullcalendar

Issue #6338: Chrome 91 update breaks fullcalendar when using a slotWidth value that is less than 20
Created: 2021-05-28T11:53:26Z
Reduced Test Case
"not reproducible with a link"
Bug Description
Set your slotWidth value to something less than 20 and make sure your on version 91 of chrome. When you do this for some reason the entire calendar stops working. You cannot drag, you cannot resize, the only thing that you can do is click on the event.
I have tested changing versions of chrome and it is definitely related to something released in the chrome 91 update however google have not released their changes as of yet.

Duplicate issue #6345: Bug in timeline view after chrome 91 update
Created: 2021-05-31T15:06:22Z
Reduced Test Case
"not reproducible with a link"
Bug Description
Since the Chrome 91 update, the grids of my calendar are bigger and the selectable lines doesn't take the entire width. Is anyone faced the same issue ? I don't know what to change in my jquery script.
FullCalendar version : 3.10.2
`$('#calendar').fullCalendar({
  header: {
    left: 'fakeButton prev,next today',
    center: 'title',
    right: ''
  },
  customButtons: {
    fakeButton: {
      text: 'date-picker-placeholder'
    }
  },
  nowIndicator: true,
  defaultDate: calendarDate,
  defaultView: 'timelineDay',
  scrollTime: '07:00',
  slotDuration: '00:15:00',
  editable: true,
  lazyFetching: false,
  selectable: true,
  selectHelper: true,
  slotLabelFormat: 'H:mm',
  resourceAreaWidth: '16%',
  aspectRatio: 2,
  resourceLabelText: 'users',
  resourceGroupField: 'userGroup',
  resourceOrder: 'title',
  slotWidth: 22,
  views: {
    day: {
      titleFormat: 'dddd D MMMM YYYY'
    }
  }, [...]`

Screenshots
Before the update

After the Chrome 91 update

Closing comment (2021-06-03T01:28:01Z): seems related to #6338
Repository: fullcalendar/fullcalendar

Issue #3593: When event data requested, pass-in timed moments
Created: 2017-03-23T01:43:01Z
Currently, ambiguously-timed moments are being misused. The requested range of time is discrete, not ambiguous.
Events function:
events: function(start, end, timezone, callback) {
    start.format(); // should be '2017-03-22T00:00:00' not '2017-03-22'
}
JSON feed:
should be
/myevents.php?start=2017-03-22T00:00:00&end=2017-03-23T00:00:00

Duplicate issue #4219: Event(as a json feed) and Agenda View GET params for start and end issue
Created: 2018-06-18T09:45:54Z
In one of the documents for events, it stated that
"FullCalendar will determine the date-range it needs events for and will pass that information along in GET parameters.
The GET parameter names will be determined by the startParam and endParam options. ("start" and "end" by default).
The values of these parameters will be ISO8601 date strings (like 2013-12-01). For precise behavior, see the timezone docs."
One of the example is
/myfeed.php?start=2013-12-01&end=2014-01-12&_=1386054751381
However, while in agenda view (agendaWeek or agendaDay), the start and end params would be passed along with timestamp as well when I exceeded the cached time period of the month.
eg. the calendar is first loaded in month view with the following url
/myfeed.php?start=2014-12-01&end=2014-12-31&_=1386054751381
Then when we switch to agendaWeek view, this would be the url and it load properly.
/myfeed.php?start=2014-12-01&end=2014-12-07&_=1386054751382.
However, when we shift previous week in agendaWeek beyond 2014-12-01, the params passed to back end would consist of
/myfeed.php?start=2014-11-24T00:00:00&end=2014-11-30T00:00:00&=1386054751383.
instead of
/myfeed.php?start=2014-11-24&end=2014-11-30&=1386054751383.
Is there any inconsistency of the date and datetime in the method to GET parameters?
or is there any missing setting like timezone:false to call only the date in the URL?
Thanks,
jy

Closing comment (2019-03-06T23:03:02Z): dup of #3593 i believe
i won't fix this in v3, but it's already fixed in v4beta
Repository: fullcalendar/fullcalendar

Issue #1037: Robust options to control initial scroll
Created: 2015-08-19T11:16:06Z
Originally reported on Google Code with ID 768
Usability issue in all browsers.

When you go to prev/next month/day in the week/day views, it pops back to the hour
as specified in the firstHour option regardless of where you scrolled to on the previous
date range. I think this is a little too presumptuous.  In my case, I want it to retain
the current scrollTop when navigating date ranges.  Other people might want to mimick
Google Calendar and scroll so that the current time is in view.

The issues is caused by the logic in resetScroll function.

I vote for creating an option called autoScroll with the following values:
- first - the first hour of the day which would be the default to maintain backwards
compatability
- current - will scroll to the current time of day like Google Calendar
- remember - will remember where you scrolled to in the previous date range
- none - will do no scrolling logic


Reported by rbohn@versatile.com on 2010-12-22 13:07:25
Imported with 4 stars.

Duplicate issue #7787: [v7-beta] `dayGridYear` no longer scrolls to current month initially
Created: 2024-10-04T02:26:12Z
Reduced Test Case
https://ovits.com.au/fc7.html
Do you understand that if a reduced test case is not provided, we will intentionally delay triaging of your ticket?

 I understand

Which connector are you using (React/Angular/etc)?
No connector (vanilla JS)
Bug Description
Hi
Just trying out the beta and noticed the default on dayGridYear is no longer "today" but now appears to be start of year (January).
Reduced test case not working (with 7: https://ovits.com.au/fc7.html)
Reduced test case working (with 6.1.15: https://ovits.com.au/fc6.html)
Did not see this mentioned in notes
This is an awesome tool and love seeing it being updated.
Let me know if need more info or I missed something obvious.
Cheers
Pete

Closing comment (2024-10-07T23:20:22Z): It does seem preferable for it to scroll to the current month so I believe it's a bug that it doesn't do that in v7.  Related to:
#1037
Repository: fullcalendar/fullcalendar

Issue #2536: Better accessibility with screen readers
Created: 2015-08-19T12:32:42Z
Originally reported on Google Code with ID 2271
Inspired by issue 2268. Should research ways to make FullCalendar a better experience
for users with screen readers. Maybe some HTML microformat that does this?

Reported by adamrshaw on 2014-09-01 22:13:56
Imported with 3 stars.

Duplicate issue #5288: Add tab stops to events for 508 compliance
Created: 2020-03-02T18:18:37Z
Bug Reports
When using the fullcalendar it will not have tab stops on the calendar events. With the laws regarding 508 compliance, the events should have a tab stop in order to be 508 compliant.
Feature Requests
Recommended change is that the links that are used as the events within the calendar have a href attribute added to them to allow for tabbing to each event and then to also include and aria-label attribute that includes the Date and what the event describes.
I.E. <a class="fc-day-grid-event fc-h-event fc-event fc-start fc-end" href="#" aria-label="Monday March second 2020, Doctor's Appointment">Doctor's Appointment</a>
This is not specific to any of the three,  but I am using Vue when I noticed this.
How I am using it in vue is <FullCalendar :events="events" v-show="this.selectedSchool.SCHOOL_ID !== ''" defaultView="dayGridMonth" :weekends="calendarWeekends" :plugins="calendarPlugins" ref="calendar" @datesRender="loadEvents" />

Closing comment (2021-08-17T20:21:54Z): Related to #2536
You could add tab stops using eventRender, eg:
https://codepen.io/acerix/pen/qBdXdzm?editors=0010

In your render function, if use use
info.el.tabIndex = info.event._instance.instanceId;
It will attach a chronological order to your tab index and control the tab through better
Repository: futo-org/android-keyboard

Issue #23: Quickly Capitalize Word When Cursor Is at End of Word
Created: 2024-06-13T21:31:34Z
Coming from Swiftkey, I'm finding a huge usability miss when trying to upper/lowercase a word
If I type a word and the cursor is at the end of that word, I would like if the shift button (capitalize button?) uppercased the word, and inversely if the word is already uppercased, lowercase it

Duplicate issue #474: Add Option to Capitalize Words with Shift Key While Typing
Created: 2024-08-15T16:01:21Z
Use Cases
It's annoying that you have to select the word to capitalize it after it has been written
Proposal
Samsung Keyboard let's you capitalize words just by placing the marker on the word and pressing the shift/caps key, and also capitalize words are added to suggestions while writing by pressing the shift/caps key
References
No response

Closing comment (2024-11-03T00:49:22Z): Duplicate of #23 - merging this request into that one.
Repository: futo-org/android-keyboard

Issue #75: More Subtle Key Pop-Ups
Created: 2024-06-29T22:09:42Z
I really love the keyboard so far, but the key popups are extremely distracting, especially in dark mode. A more subtle option such as how gboard does it would be really good

Duplicate issue #312: Resizeable Pop-Up on Key Press
Created: 2024-07-19T01:07:56Z
A slider to make the pop ups a bit smaller would be nice.

Closing comment (2025-04-19T15:45:03Z): The size was updated in one of the updates to be less wide, for a more Gboard-like style closing as duplicate of #75
Repository: futo-org/android-keyboard

Issue #835: Key-By-Key Customization for Keyboard Layout and Long-Pressing
Created: 2024-11-18T02:38:30Z
Use Cases
Many users have requested the ability to customize long-press behaviors in the keyboard. This would make it easier for users to transition from Samsung, iOS, and other operating systems that have different keyboard layouts than FUTO. This would be easier for many users than creating their own custom layout if layout customization was built right into the UI of the app.
Proposal
There could be a Customize Layout feature in settings, which would allow users to drag and drop keys to different areas of the keyboard, assign their long-pressing functions, etc.
References
No response

Duplicate issue #924: Customize Actions for Long-Pressing `Enter`
Created: 2024-12-07T20:56:07Z
Use Cases
Long-pressing Enter provides some actions.
Proposal
Let user customize these.
References
No response

Closing comment (2024-12-10T23:25:58Z): Closing as duplicate of #835
Repository: futo-org/android-keyboard

Issue #683: Support Multi-Lingual Typing Without Layout Change
Created: 2024-06-20T16:21:33Z
I write in spanish and english frequently. In Gboard and florisboard you can use the same keyboard layout (spanish for example) to write in multiple languages and get corrections  and suggestions for both or more languages. Currently in FUTO keyboard if I want to write something in english while on the spanish layout it will auto-correct the words to spanish.
I imagine that this could be fixed adding a function to reference multiple language dictionaries at the same time. Not necessarily linked to the current layout.
This is probably possible through the dictionary override feature, but it would be better if I could choose to add another of the existing language dictionaries directly from within the app.
Cheers!

Duplicate issue #158: Multilingual Autocorrect: recognize language in-real time
Created: 2024-07-03T23:38:10Z
I think autocorrect/suggested words can be improved in multilingual keyboards, perhaps it could try to identify which language is being used and automatically switch autocorrect/suggested words to the current language being written.

Closing comment (2024-07-06T09:51:07Z): likely duplicates #683
Yep, duplicate.
Thanks.
Repository: futo-org/android-keyboard

Issue #125: Backup and Sync Feature for Settings and Dictionary
Created: 2024-07-02T12:36:49Z
Not as if there's an excessive number of options (currenly) but an obvious addition that doesn't seem to be on the roadmap is a simple data import\export, cloud options would be unnecessary but nice.
Thank you

Duplicate issue #1256: Local Backup the Settings
Created: 2025-04-23T14:18:41Z
Use Cases
Proposal:
Give an option to local backup the settings to the device storage for quick share, easy setup for new device.
Make sure to give flexibility to choose where we have to save the backup.
Additional context:
If it is possible, try for "Auto backup".
Proposal
No response
References
No response

Closing comment (2025-04-23T22:46:29Z): Duplicate of #125 and #643
Repository: futo-org/android-keyboard

Issue #295: Add Versioning and Metadata for Voice Input Models
Created: 2024-07-16T22:08:58Z
The models available here should be versioned with a datestamp:

https://keyboard.futo.org/voice-input-models

This datestamp metadata should also be presented to the user in the relevant options area, so they do not lose track of which external model they've loaded.

Duplicate issue #1272: Show version & release date for voice input models
Created: 2025-05-02T20:12:21Z
Use Cases
When downloading a voice input model, the documentation only shows the model's size (e.g. English-74)
Without a release date or version number, users can't know if a new model was released. Including the release date (e.g., 2025-04-18) next to each download would clarify this.
Proposal
No response
References
No response

Closing comment (2025-05-04T17:44:50Z): Duplicate of #295
Repository: futo-org/android-keyboard

Issue #154: Auto-Capitalization on Swipe Typing Causes All-Caps Words
Created: 2024-07-03T18:58:46Z
When the option for Auto Capitolization is enabled and I use swipe typing it will make every word typed using swipe all caps. I switched auto caps on and off and it fixed the issue for now.

Duplicate issue #286: Keyboard Frequently Enables Caps Lock Unexpectedly
Created: 2024-07-16T06:25:18Z
Maybe just me but when I return to any app (eg whatsapp) I noticed the caps lock is on.
Not sure why but ban we get an option to disable this?

Closing comment (2024-10-23T23:33:46Z): Duplicate of #154 - see that issue for details.
Repository: futo-org/android-keyboard

Issue #755: Change Language of the UI
Created: 2024-11-02T17:17:33Z
Use Cases
The UI (settings, etc.) defaults to system, but in my case it is barely translated (polish), causing a mix of untranslated and translated menus
Proposal
A setting to change the language, or simply to force english, which should be enough for most users
References
No response

Duplicate issue #1091: Add the Ability to Translate the Keyboard App Into Different Languages
Created: 2025-02-03T18:05:20Z
Use Cases
The program is ~90% not translated into other languages, because all the text is written in smali
Proposal
Please put all the lines for translation in a string.
I would also like to help with translating the program into Russian
References
No response

Closing comment (2025-02-03T19:42:13Z): Closing as duplicate of #755
Repository: futo-org/android-keyboard

Issue #560: Swipe Typing Fails for Long and Complex Words
Created: 2024-09-19T15:10:07Z
What happened?
Swipe typing a word which involves complicated swipes like:

actually
manipulation
bizarre
entryway
complicated
successfully

I swipe these carefully and see the pattern contact each letter, but it's hit or miss. You feel like you successfully swiped it, and see the swipe trail, but there is no response from the app at all.
Other times in the same session, the predictor finds them instantly.
Speech to text is working perfectly, but I suspect most Android users swipe and this makes adopting the app very difficult.
Keyboard Version
0.1.23.2 playstore
Text field info
No response

Duplicate issue #661: Swipe Misrecognizes Finnish 'Minä' but Detects 'Mina' Instead
Created: 2024-10-19T16:11:43Z
What happened?
Keyboard layout: Nordic (å, ö, ä-cluster to the right)
"a" is on the left, "ä" is on the right of the keyboard
Case Alpha

Swipe "Minä"
Suggested words "Mum" (only suggested word)
Should've been suggested: "Minä"

Case Bravo

Swipe "Mina"
Suggested words: "Minna", "minä", "miina"
Should've been suggested: "Minna", "miina", other

Notes:

I don't speak Finnish
I think Case Alpha is worse than Case Bravo
I don't know what Finnish speakers expect or think of Case Bravo
This also happens with Norwegian using an æøå-cluster. «Håret» is detected when swiping «Haret»

Dictionary: The Suomi-dictionary suggested by FUTO keyboard
Keyboard Version
v0.1.23.s-playstore

Closing comment (2024-10-24T16:58:49Z): Similar to #560 - merging this issue into that one. See #560 for details.
Repository: futo-org/android-keyboard

Issue #553: Incorrect Spell Check When Typing in Non-System Languages
Created: 2024-09-15T21:47:59Z
What Happened?
When the keyboard is set to a language different than the system language, most words will wind up being marked as misspelled in a pretty significant number of contexts. That's an Android issue, but it's pretty normal for me at this point.
When selecting a genuinely misspelled word, FUTO seems to fall back on the system dictionary rather than its internal dictionary for the current keyboard language. This often results in French language suggestions when I'm typing in English.
I am specifically using Android 14 on an Asus Zeonfone 9.
Keyboard Version
1.23.2
Text field info
No response

Duplicate issue #768: Grammar Correction When Language Changes is Broken 
Created: 2024-11-05T07:46:24Z
What happened?
I have 2 languages in FUTO keyboard (and also 2 languages in Android). When I use English (the primary language in Android) everything is ok. When I switch to my second language on the keyboard the grammar correction in the text field is in the primary language.
This only happens with FUTO keyboard.
Keyboard Version
0.1.24
Text field info
it happens in every text field

Closing comment (2024-11-07T20:27:07Z): Duplicate of #553 - merging this issue into that one.
Repository: gantry/gantry5

Issue #1125: 404 Outline not found
Created: 2016-01-28T08:59:51Z
Hello,
This new version (5.2.8) breaks "infolist" particle ability to add links to each item. I was modifying the footer in the RocketLauncher of Requiem (the "Useful links" part) and when I changed the link it said "404 Outline not found". I reverted temporarily to 5.2.7 and it worked fine.

Duplicate issue #1135: Error while saving layouts in outlines using Hydrogen theme 5.2.9 with gantry 5.2.9
Created: 2016-02-05T17:10:35Z
When ever I try to save/update layout in the outlines it shows a popup and says

404 View not found [name, type, prefix]: category, json, contentView

Please help as I love gantry and would love to use the theme.
Attach is the screen shot of the error I get.

Closing comment (2016-02-07T07:18:17Z): seems related to #1125
Repository: gantry/gantry5

Issue #557: Mobile Menu on Android/Firefox not working consistently
Created: 2015-07-10T10:56:29Z
Further to #553 and conversations with @kat05 @mahagr
It would appear that mobile menu on Adroid 4.1.2 in firefox 39 and Android 4.2.x does not work reliably. sometimes requiring multiples taps.
Collectively we feel that we should have another look at this to see if anything can be done.
This is forum link http://www.rockettheme.com/forum/joomla-template-callisto/244530-firefox-android-does-not-open-second-level-items-in-mobile-menu?start=0#1217081

Duplicate issue #662: Use of iframe breaks Offcanvas button function on Android Firefox
Created: 2015-07-28T16:48:57Z
http://www.rockettheme.com/forum/joomla-template-callisto/244247-mobile-navigation-not-working-on-firefox-for-android?start=10
The issue with the offcanvas menu not opening (clicking the hamburger icon won't show the menu) on android firefox has been narrowed down to the use of iframe.
It seems that even embedding a youtube video on the site breaks the functionality.
The code in question sits in a custom_html module with the following code:
<div><iframe src="//www.youtube.com/embed/EKHvlojQJFU" width="550" height="309" frameborder="0" allowfullscreen="allowfullscreen"></iframe></div>

Closing comment (2015-08-04T10:38:50Z): This is no duplicate of #557. In that issue Android/FF was tested with a clean Rocketlauncher install without a youtube iFrame placed in a custom_html module.
Offcanvas menu is working on all pages without iframes and not working on the pages with. After de-publicating the modules with iFrames the offcanvas menu is working everywhere!
Tested and able to reproduce the issue over and over again on Genymotion virtual device Google Nexus 4 running Android 4.4.4 and 5.0.0
Repository: gantry/gantry5

Issue #1301: Issue when posting/sending a BreezingForm
Created: 2016-05-23T15:15:18Z
@mahagr Hey Matias,
One of our customers reported an issue when using BreezingForms with Gantry 5.
As soon as the user tries to submit the form, the whole module position the form is published to gets corrupted and the following error message is shown:
Error while rendering position.

The issue is reproducible with Hydrogen as well.
Have a look at this video, it shows everything.
What could be causing the issue? I guess the action that BreezingForms perform when submitting the form is in conflict with the way Gantry 5 renders the module positions.
Currently, because of that issue, BreezingForms cannot be used with Gantry 5.
Thanks for looking it this ;)

Duplicate issue #1303: Issue when submitting a BreezingForm
Created: 2016-05-23T15:22:05Z
@mahagr Hey Matias,
One of our customers reported an issue when using BreezingForms with Gantry 5.
As soon as the user tries to submit the form, the whole module position the form is published to gets corrupted and the following error message is shown:
Error while rendering position.

The issue is reproducible with Hydrogen as well.
Have a look at this video, it shows everything.
What could be causing the issue? I guess the action that BreezingForms perform when submitting the form is in conflict with the way Gantry 5 renders the module positions.
Currently, because of that issue, BreezingForms cannot be used with Gantry 5.
Thanks for looking it this ;)

Closing comment (2016-05-23T17:19:36Z): Duplicate of #1301