5886 - events on :before and :after not going to parent

Status: VERIFIED FIXED

(Core :: DOM: UI Events & Focus Handling, defect, P3)

Description

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Since :before and :after should, I think, work just as events do on child
elements.  That is, events sent to the :before in

<a><:before>pseudo-text</:before>more-text</a>

should work just as those sent to em in:

<a><em>em-text</em>more-text</a>

In the former case, links to not work.  Clicking or hovering over pseudo-text
shows no link behavior (see above URL).  However, the latter case works.  I
think they should both work like the latter case since :before and :after
create a new first-child and last-child in a formatting sense.

Comment 1

[Heikki Toivonen (remove -bugzilla when emailing directly)]

So what is the situation with this bug?

David's example is great in that it points out inconsistet behaviour. Also, XML
can have empty elements (no content even allowed). If such an element happend to
be a link element, for example, the link would be unusable if this bug was not
fixed. Simply because of this limitation on XML I even considered setting the
severity to major...

Wouldn't it be simple to fix this? Just pass on the events from the generated
content to its effective parent element?

Comment 2

[jst]

Attachment: Patch that makes events go from generated content to its parent, ie fixes the bug

Comment 3

[Heikki Toivonen (remove -bugzilla when emailing directly)]

I hate doing this, but... There is a really small patch attached that fixes this
problem, so what is taking so long? Perhaps more importantly, why is there not a
target milestone, I think M11 would be resonable? I'll set it to M11 now, yell
at me if I should not be touching target milestone fields...

Comment 4

[troy]

*** Bug 5349 has been marked as a duplicate of this bug. ***

Comment 5

[Hixie (not reading bugmail)]

Bug 5349 is the same problem applied to alt text of broken images in links;
since alt text is internally treated as generated content this is the same
problem.

Comment 6

[troy]

Changed CreateGeneratedFrameFor() to set the parent object and the document
object of the generated content

Comment 7

[Jan Carpenter]

verified