Closed
Bug 90649
Opened 23 years ago
Closed 20 years ago
content generated twice by :after/:before for OBJECT
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
WORKSFORME
Future
People
(Reporter: glazou, Assigned: dbaron)
References
(Blocks 1 open bug)
Details
(Keywords: css2, testcase, Whiteboard: [HTML4-13.3])
Attachments
(1 file)
1.84 KB,
text/html
|
Details |
Any textual content generated by html elements FORM, BUTTON, LABEL, LEGEND and OBJECT using pseudo-elements :before and :after is generated twice. Of course, it should be generated only once... See test case attached. This bug blocks revamping of AllTags mode in Composer (bug 88036).
Reporter | ||
Comment 1•23 years ago
|
||
Assignee | ||
Comment 2•23 years ago
|
||
See bug 69398. (I think the root cause is that we implemented :before and :after for replaced content as outside-the-box, even though they're supposed to always mean inside-the-box and should not work for replaced content despite what the spec says.)
not a table specific bug, reassigning to core owner.
Assignee: karnaze → attinasi
Comment 4•23 years ago
|
||
Reassigning to John
Assignee: attinasi → jkeiser
Target Milestone: --- → mozilla1.1
David: which part of the CSS2 spec covers what you said in comment 2 ?
Assignee | ||
Comment 6•22 years ago
|
||
The patch on bug 141289 fixes everything except OBJECT.
Assignee | ||
Comment 7•22 years ago
|
||
To fix object we probably need to have nsCSSFrameConstructor::CantRenderReplacedElement pass an additional parameter (or something in the state object?) to nsCSSFrameConstructor::ConstructFrameByDisplayType so that it can pass PR_FALSE to nsCSSFrameConstructor::ProcessChildren for the boolean parameter about whether to construct generated content.
Comment 8•22 years ago
|
||
How odd. The testcase now WFM for all cases, including OBJECT. Did this get fixed in another bug?
Assignee | ||
Comment 10•22 years ago
|
||
Oh, *including*. Perhaps it was fixed by bug 141054.
Comment 11•22 years ago
|
||
In the following testcase, 'X' and 'Y' are displayed twice with 2002073008-trunk/Linux. http://bugzilla.mozilla.gr.jp/showattachment.cgi?attach_id=983 But I can't reproduce the bug with attachment 42175 [details].
Comment 12•22 years ago
|
||
The current testcase is now broken again in Mozilla 1.1, for <object> only.
Keywords: html4
Whiteboard: [HTML4-13.3]
Comment 13•21 years ago
|
||
Hmm... I bet this happens because we give the child frame the same style context as the object frame itself has....
Assignee | ||
Comment 14•21 years ago
|
||
-> style or frame construction
Assignee: john → dbaron
Component: Layout → Style System
QA Contact: petersen → ian
Comment 16•20 years ago
|
||
This is a WFM now, although I think Mozilla should disable generated content on replaced elements, since it is wrong (20040227, WinXP).
Keywords: html4
Comment 17•20 years ago
|
||
> although I think Mozilla should disable generated content on replaced elements We have, actually, more or less. See bug 169334
Comment 18•20 years ago
|
||
Replaced-element cannot have :before/:after contents. WFM?(or FIXED?)
Comment 19•20 years ago
|
||
(In reply to comment #18) > Replaced-element cannot have :before/:after contents. > WFM?(or FIXED?) Therefore, it is still a bug, haven't you checked the test cases?
Comment 20•20 years ago
|
||
? This bug description is "content generated twice by :after/:before for OBJECT". The problem in the description cannot be reproduced on my environment.
Comment 21•20 years ago
|
||
So the one possible issue I see with the testcase is that <button> has generated content. The other things are all correct, no?
Comment 22•20 years ago
|
||
I see the problem of button element. However, I think that the problem should be separated another bug or this description should be changed.
Comment 23•20 years ago
|
||
I see it on both the BUTTON and the OBJECT element. (WinXP)
Summary: content generated twice by :after/:before for OBJECT → remove support generated content on replaced elements
Updated•20 years ago
|
Attachment #42175 -
Attachment description: test case showing content generated twice instead of once → test case
Comment 24•20 years ago
|
||
Anne, the button issue should go into a separate bug, as Masayuki Nakano says (it's not clear the <button> is a replaced element....). For the <object>, are you seeing the before/after when the plugin runs? Or only when the alternate content is shown? I only see it when the alternate content is shown, which is correct.
Comment 25•20 years ago
|
||
Undoing bogus summary change. Don't morph bugs, mmmkay?
Summary: remove support generated content on replaced elements → content generated twice by :after/:before for OBJECT
Comment 26•20 years ago
|
||
Per comment 24: -> WORKSFORME
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Comment 27•20 years ago
|
||
The plugin runs in my environment.
Reporter | ||
Comment 28•20 years ago
|
||
As reporter of the bug, I confirm the WFM with my 20040415 WinXP build and agree with bz that the summary of this bug should not change, representing precisely the original problem, complete blocker for some changes in AllTags mode of Composer. Detail unrelated to this bug but of interest for many people observing it: BUTTON creates generated content that way: [<button>this is a button</button>] where the square brackets materialize the button's border. That's absolutely normal. But I need <button>[this is a button]</button> So I hardly wait for CSS3 generated content's implementation. ;-)
You need to log in
before you can comment on or make changes to this bug.
Description
•