Closed
Bug 257129
Opened 21 years ago
Closed 21 years ago
:before and :after in conjunction with "content:" doesn't parse HTML special characters
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 204324
People
(Reporter: lordwo, Assigned: dbaron)
References
()
Details
User-Agent: Opera/7.54 (Windows NT 5.2; U) [en]
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3
When using the CSS property "content:" in conjunction with any of the :before of
:after pseudo-elements, if the code specify some HTML special characters
beginning with an ampersand (&), those characters are not correctly parsed and
displayed raw.
I've created a special html page in order to reproduce the bug.
Opera (Win/Linux) and IE6 seems to correctly handle this.
Further symptom of the problem is that the text added in the document via :after
{ content: addedtext } seems not te be selectable with the mouse.
Problem also appears on:
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.1) Gecko/20040707 Mozilla 1.7.1
Reproducible: Always
Steps to Reproduce:
1. Load the page
2. Breathe
3. Open your eyes
Actual Results:
You can see that the HTML special characters are not parsed in this case,
meaning ampersands and strange codes appearing in the document.
Expected Results:
The software should have parsed and replaced the special characters according to
existing conversion tables.
Comment 1•21 years ago
|
||
This is a DUPLICATE of a bug marked INVALID. Looking for it...
Comment 2•21 years ago
|
||
There was another one too, but this one seems correct.
*** This bug has been marked as a duplicate of 204324 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•