Opened 6 weeks ago
Closed 3 weeks ago
#64165 closed defect (bug) (reported-upstream)
At A Glance, You Can't Tell Which Blocks Have Notes And Which Don't
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 6.9 |
| Component: | Notes | Keywords: | |
| Focuses: | Cc: |
Description
In the following screenshot, a number of these blocks have Notes attached to them. But you can't tell. There are a handful of notes in the panel, but there's no way to tell which one belongs to which block without clicking on them, which may be the way it's supposed to work.
However, figuring out which blocks have comments and which don't requires the user to click on all of them. Even if the Visual Indicator is the Small avatars in the block's toolbar, it doesn't help distinguish, at a glance, which blocks have notes and which don't.
Attachments (1)
Change History (8)
#1
@
5 weeks ago
This is great feedback @jeffr0 - thanks for the bug report.
We discussed adding icons over the blocks indicating the notes as one possible solution. If you go into the "floating" mode by closing the Notes panel, the notes float alongside their related blocks which makes it easier to tell which blocks have comments.
Hovering over notes does highlight their related block, but this doesn't really address your question "Which blocks have comments"?
#3
@
5 weeks ago
I'm wondering what we should do with this ticket. Should we perhaps close this and submit an issue to Gutenberg instead?
#4
@
4 weeks ago
- Milestone changed from 6.9 to 7.0
Regarding this ticket, I believe further discussion is needed, and we need to explore solutions.
Since the RC1 release is coming soon, let's punt this ticket to version 7.0.
#5
@
4 weeks ago
- Component changed from General to Notes
Moving tickets related to the new Notes feature into the new Notes sub-component under Comments.
#6
@
3 weeks ago
With Notes still being iterated on in the Gutenberg codebase, should this get moved as an upstream issue in GitHub or kept here (and worked on in wordpress-develop)?
#7
@
3 weeks ago
- Milestone 7.0 deleted
- Resolution set to reported-upstream
- Status changed from new to closed
With Notes still being iterated on in the Gutenberg codebase, should this get moved as an upstream issue in GitHub or kept here (and worked on in wordpress-develop)?
I think this requires some development on the editor side, so let's move it upstream. I've submitted an issue: https://github.com/WordPress/gutenberg/issues/73414
Can't tell the difference between blocks with notes and blocks without them