Closed Bug 109093 Opened 24 years ago Closed 4 months ago

Inability to click/select in between objects in Composer

Categories

(Core :: DOM: Selection, defect, P5)

Product:
Core
Component:
DOM: Selection
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX
Milestone:
Future

People

(Reporter: imajes, Unassigned)

References

(Blocks 1 open bug)

Details

Right now, it's not possible to position the caret inbetween objects to select them, in composer. This then requires workarounds to provide enough space for the caret to be drawn. This shouldn't need to happen, and as such needs fixing. :)
-> selection
Assignee: attinasi → mjudge
Component: Layout → Selection
QA Contact: petersen → tpreston
should this be editorbase? is it a duplicate?
setting to future.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Assignee: mjudge → nobody
Status: ASSIGNED → NEW
QA Contact: tpreston → selection
Joe, can you reproduce this and bug 105684?
Without the ability to see the html tags, selection is a hit or miss affair. You have no idea what you are really selecting when you swipe. What we really need is a visible representation of the actual html with tags as in seamonkey composer. Without that selection will always be a shot in the dark.

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority and severity.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: -- → P5

I think we cannot fix this bug for any objects.

Here is a testcase with 2 <img> elements. When I click right-half of the left <img> or left-half of the right <img>, indeed, I may expect that the caret should appear between the <img>s. However, I believe that it may be unexpected behavior if and only if I want to edit the <img>'s property with editing UI implemented by Thunderbird or the web app. So, it depends on the user's current expectation that which behavior is suitable.

One possible idea is, rightmost quarter and leftmost quarter should not select the <img>. However, it may be unexpected one for the user in some cases. Additionally, it's hard to do it if the <img> is too small to click. So, I don't think we should do that unless some developers really love to do that.

So, I mark this as WONTFIX. If you want to fix this bug by yourself, please reopen this bug and take this.

Note that on Chrome, clicking on <img> works odd. It's hard to find how they handle it. So, please check the behavior within the testcase.

Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.