184516 - Hover events don't allow generated content unless it's been "pre-set"

Status: RESOLVED FIXED

(Core :: CSS Parsing and Computation, defect)

Description

[Eric A. Meyer (dead account)]

This was a tough one to summarize-- hopefully someone will be able to do a
better job.  Combinations like 'a:hover:before' do not actually insert the value
of the 'content' property except in certain circumstances.  Thus:

   a:hover:before {content: "->";}

...does not actually do anything when an 'a' element is hovered.  However, if I
write:

   a:before {content: "";}
   a:hover:before {content: "->";}

...then Gecko acts as expected.  Testcase to follow.
   This was tested with 2002120203/MacOS9.1.  Searches for open
generated-content bugs showed nothing that seemed similar to this.

Comment 1

[Eric A. Meyer (dead account)]

Attachment: Testcase showing various behaviors

Comment 2

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

We have general problems with dynamic changes and generated content.  Boris has
a bug on that and has a (partial?) patch.

Comment 3

[Boris Zbarsky [:bzbarsky]]

Yeah, patch in bug 126072 fixes this.

Comment 4

[Boris Zbarsky [:bzbarsky]]

fixed by checkin for bug 126072