Closed
Bug 20080
Opened 25 years ago
Closed 22 years ago
{ib}style not inherited inside floated span
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
Future
People
(Reporter: ian.graham, Assigned: attinasi)
References
()
Details
(Keywords: css1, testcase, Whiteboard: [Hixie-P3])
Attachments
(1 file)
3.03 KB,
text/html
|
Details |
Given <a href="...."><span>some text</span>more text</a> Then the cursor property should be inherited inside the span -- or at least that's what I would expect to happen. This does not always take place, as illustrated in the URL-referenced document. An example illustrating the bug is shown in (B). Here, the span is floated to the left: the resulting span content is active (it works as a link), but does not inherit the cursor property corresponding to a link. As (C) shows, an explicit cursor:inherit declaration fixes this -- but since cursor is by default inherited (see Section 18.1), this should not be needed .... Also, as shown in (D), if the text content of the span is replaced by an img, then the span content _does_ inherit the 'pointer' cursor from the anchor element. Tested on Nov 20 nightly build...., Windows 98.
Comment 1•25 years ago
|
||
Testing the URL, in none of the 4 testcases provided did the cursor over an anchor become the proper "hand pointing" cursor whether over the span or not. The reason for this is probably the same reason that none of the Anchor links work, which is probably bug 21186 "[DOGFOOD] Can't click on links in CNET story" (also has <span> inside <a>, see comments ). As it is and at present the testcases are untestable. Tested with: 1999-12-14-08-M12 nightly binary on Windows NT 4.0sp3 Suggest making this bug dependent on bug 21186.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M15
Comment 2•25 years ago
|
||
Agreed: marked as dependent of bug 21186. Thanks, Ian, for the excellent testcase.
Comment 3•25 years ago
|
||
Pushing my M15 bugs to M16
Updated•24 years ago
|
Target Milestone: M16 → M18
Comment 4•24 years ago
|
||
Comment 5•24 years ago
|
||
This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug, or if it blocks your work in some way -- please attach your concern to the bug for reconsideration.
Target Milestone: M18 → Future
Updated•24 years ago
|
Assignee | ||
Comment 6•24 years ago
|
||
This is a dup of 51113, which is a more general statement of the problem with a patch. *** This bug has been marked as a duplicate of 51113 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 8•24 years ago
|
||
This bug is not fixed in Mozilla 0.7 (WIndows 98R2) as indicated by viewing the test case http://smaug.java.utoronto.ca/NS5-bugs/cursor-inherit-test.html (note that the 'attached' test case is missing an image file). First look to Example (b). The underline initially should, and does, span the entire anchor. But if the mouse moves over the link, the underline vanishes from the text inside the <span>, and does not return when the mouse moves off the link. I believe this is a rendering bug. This is not an inheritance bug, as the underline should be a property of the <a> element, and should be drawn under the <span> content, and have the same f.g. color as the <a> (which it does, at least until it disappears ;-) ) There is also an inheritance bug, however, as the cursor type inside the <span> should (by default) inherit from the parent <a>, and does not. Example (C) is similar, except in this case mousing over and off the anchor causes both the background color and underline for the <span> to vanish. Ian (the other one) will be able to verify whether or not these are all CSS bugs, or perhaps my misinterpretation of hte CSS1/2 specs. But, regardless of interpretation, the browser shouldn't render the content differently before and after the mouse rolls of the link.
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
Comment 9•24 years ago
|
||
Netscape's standard compliance QA team reorganised itself once again, so taking remaining non-tables style bugs. Sorry about the spam. I tried to get this done directly at the database level, but apparently that is "not easy because of the shadow db", "plus it screws up the audit trail", so no can do...
QA Contact: chrisd → ian
Reporter | ||
Comment 10•24 years ago
|
||
For additional (I hope) clarity, I've prepared a second test case, http://smaug.java.utoronto.ca/NS5-bugs/cursor-inherit-test2.html, that has text nodes before and after the floated <span>. This demonstrates the same bugs, but at least puts the floated span on a new line.
Updated•23 years ago
|
Whiteboard: [Hixie-P3]
Comment 11•23 years ago
|
||
The remainer part of this bug is not a problem with the cursor but a rendering problem with floating elements. The floating spans don't inherit the style correctly. It is related to the fact that floating inline elements should be displayed as blocks (see EnsureBlockDisplay()) but then we end up with a block element which should be considered style-wise as a child of the inline anchor element. Ian: am I correct? Marc: do we want to fix this? At the best, I would leave it Future but I won't mind if you mark it WontFix.
Assignee: pierre → attinasi
Status: REOPENED → NEW
Updated•23 years ago
|
Summary: cursor: inheritance bug: not inherited inside floated span → style not inherited inside floated span
Summary: style not inherited inside floated span → {ib}style not inherited inside floated span
Comment 13•22 years ago
|
||
WorksForMe using FizzillaCFM/2002070913. In all four tests, the cursor changes to pointer over both the anchor and the SPAN.
Comment 14•22 years ago
|
||
Works here in 2002070708 Win32 Nightly (WinXP). Resolving WFM.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago → 22 years ago
Resolution: --- → WORKSFORME
Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•