-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Comments
I think that adding upstream issue titles to the post would be useful. |
👆 You can move mouse over issue reference to get popup with details. |
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. |
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. |
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 And if we need titles, issue authors should just update this list for the issue he owns. From me it's: |
linklink
linklink
code ref, code ref
code ref
code ref
linklink
code ref
link
code ref, code ref
code ref
code ref, code ref, code ref
Status definition:
open
- issue which is opened and is waiting for beeing resolvedfixed
- issue marked as fixed and closed, but not verified/cleaned up on CKEditor sidewon't fix
- issue marked as invalid or not beeing fixed and closednot available
- private or hidden issueThe text was updated successfully, but these errors were encountered: