Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upstream issues #3779

Open
msamsel opened this issue Jan 14, 2020 · 5 comments
Open

Upstream issues #3779

msamsel opened this issue Jan 14, 2020 · 5 comments
Labels
status:confirmed An issue confirmed by the development team.

Comments

@msamsel
Copy link
Contributor

msamsel commented Jan 14, 2020

Status Platform Issue Description Link
open WebKit #699 Safari ignores nbsp in visual mode waiting for report
open WebKit #4306 Incorrect selection of elements in table link
open Webkit #4183 Inserting image with srcset into dynamically created iframe results in invisible image link
open Android #4120 Typing in Russian at the beginning of a contenteditable element replaces part of the text link
open Webkit contenteditable element does not completely surrender focus link
open Firefox #3726 Opening Findbar broke contenteditable caret moving link
open Chromium #3659, #1536 Object clipboardData.items Contains no items when Pasting File from OS link
open Chromium #3619 Text caret stop blinking after erasing the text from search box through 'Backspace' key. link
open Firefox #2968 contenteditable content is altered when pressing delete link
open Chromium #2749 Element keeps :hover state when it loses focus after click link
open Firefox #2599 Typing after selecting a complete list removes the list link
open WebKit #2280, #1926, #1899 ContentEditable=True inside of an Iframe jumps to the top of the parent window. link
open Firefox #2216 Incorrect range containers when retrieving selection for number input element link
open WebKit #2016 Empty selection with readonly contenteditable element link
open Chromium #1952 Contenteditable issues related to backspace handling link
open WebKit #1952 Contenteditable issues related to backspace handling link
open Chromium #1838 Alt text on broken images overriding css dimensions link
open Chromium #1798 Typing in a contenteditable with 100k characters is much slower than safari/firefox link
open Chromium #1590, #645 Contenteditable replaces strong tag to bold when its content become empty. No way to stop contenteditable inserting quirky style tags link
link
open Chromium #1439 Clicking outside BODY element should make selection empty link
open Firefox #1149 Can't exit links in contenteditable elements link
open Chromium #531 Styled link in contenteditable loose style when new text is append at the end of link. Typing before a link changes tag nesting order link
link
open WebKit #531 Styled link in contenteditable loose style when new text is append at the end of link. link
open WebKit #471 Nested tables inside iframe hangs Safari link
open WebKit #2374 Images from LibreOffice incorrectly pasted link
open Chromium #3879 Navigation with arrows in bidi is broken at the beginning and end of line link
open Chromium #1550 Scrollbar flicker in iframe with specific element composition. link
open WebKit #903 Context menu change selection in table, which leaks to next cell link
open Chromium text/html paste data trasnfer contains artifacts
code ref, code ref
link
open WebKit Changing CSS cursor style doesn’t have any effect while the mouse is down.
code ref
link
open WebKit Pasting of first newline into text area does not appear to work
code ref
link
fixed WebKit #1536 No information about copied image into clipboard link
fixed Chromium #2166 Noneditable element inside contenteditable inside iframe chrashes chrome when selected link
fixed Chromium #1981, #1799 Table in contenteditable doesn't display korean letter corectly. Chinese Input Method interrupt composing in Table editing. link
link
fixed Firefox #1878 Cursor misplaced in contenteditable after pressing Backspace link
fixed Chromium #1390 IFrame's scrollbars do not reappear after hiding and showing iframe link
fixed Chromium #1271 Pasting lots of text to a textarea is slow link
fixed Chromium #774 scroll doesn't work after hide and show iframe link
fixed Firefox Substring treats undefined as null for the second optional parameter. String.prototype.substr and others are not ECMA compliant
code ref
link
link
fixed Firefox Bogus <br> is inserted at the beginning of contenteditable body with non-editable block
code ref, code ref
link
fixed Firefox Only text data available when I paste content from MS Word
code ref
link
fixed WebKit [iOS] IFrames are not scrollable even when scrolling=yes is specified
code ref, code ref, code ref
link
fixed WebKit event.(dataTransfer|clipboardData).getData('text/html') (onpaste, ondrop), code ref, code ref link
won't fix WebKit #2609 Content pasted from Excel does not preserve its structure link
won't fix Chromium #1975 Selected list doesn't get deleted with cut/delete key link
won't fix Chromium #484 Triple click incorrectly places the selection range at the end of the next paragraph link
won't fix Chromium #484 Selection after a triple-click (to select the whole element) has an endContainer outside of this element link
not available IE #3735 link
not available Edge #1864 link
not available Edge #1549 link
not available Edge #1545 link
not available Edge #1536 link
not available Edge #1174 link
not available Edge #1148 link
not available Edge #1042 link
not available Edge #961 link
not available Edge code ref link
not available Edge code ref link
not available Edge code ref link
not available Edge code ref link
not available Edge #3184 code ref, code ref link
not available Edge code ref link

Status definition:

  • open - issue which is opened and is waiting for beeing resolved
  • fixed - issue marked as fixed and closed, but not verified/cleaned up on CKEditor side
  • won't fix - issue marked as invalid or not beeing fixed and closed
  • not available - private or hidden issue
@msamsel msamsel added the status:confirmed An issue confirmed by the development team. label Jan 14, 2020
@Dumluregn
Copy link
Contributor

I think that adding upstream issue titles to the post would be useful.

@msamsel
Copy link
Contributor Author

msamsel commented Jan 14, 2020

👆 You can move mouse over issue reference to get popup with details.

@Dumluregn
Copy link
Contributor

Yes but only about GH issues, doesn't work for upstream links, and just from the issue title it's not always obvious what is the upstream. And if you look for a particular one or compare them (e.g. if we ever want to group them somehow) it's not really comfortable.

@msamsel
Copy link
Contributor Author

msamsel commented Jan 14, 2020

I think that first, we should start to use the list, then improve it according to real needs. Right now we don't know if the grouping will be necessary or not or what kind of information will be useful. Premature optimizing the list might result with introducing too much unnecessary noise.
Lots of titles of those issues is not descriptive at all and will require reading the entire issue. So maybe there will be better ideas for example: name some common scopes (like selection, editing, etc.) and group or label them in such a way.

@f1ames
Copy link
Contributor

f1ames commented Jan 15, 2020

I mostly agree with @Dumluregn on #3779 (comment), now the list is quite unreadable and it's quite hard to scan through issues to search what you are looking for. It's the same as for native issues list on GH - you look on titles or use serach to narrow the list and then look on titles.

How about adding upstream issue links as titles and grouping by the browser? For example:

Chromium


As for unavailable Edge issues I checked issues I reported and all are marked private (which probably means only the author and dev team can see it) - so that may be the case for the rest too.

image

And if we need titles, issue authors should just update this list for the issue he owns. From me it's:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:confirmed An issue confirmed by the development team.
Projects
None yet
Development

No branches or pull requests

3 participants