Closed
Bug 19983
Opened 25 years ago
Closed 25 years ago
Anchor Link not working inside Label element
Categories
(Core :: Layout: Form Controls, defect, P3)
Core
Layout: Form Controls
Tracking
()
VERIFIED
FIXED
M15
People
(Reporter: chrispetersen, Assigned: rods)
References
()
Details
(Whiteboard: Fix is in my tree)
Attachments
(2 files)
Version: Apprunner Build: 1999112308 Platforms: All Expected Results: The link (created by a A element) should function when clicked on. What I got: The link is not functional. Steps to reproduce: 1) Open Apprunner 2) Select the following test case: http://slip/projects/marvin/simple/ label_a.html 3) Click on the link. Nothing happens.
Reporter | ||
Comment 1•25 years ago
|
||
Updated•25 years ago
|
Assignee: karnaze → kmcclusk
Comment 2•25 years ago
|
||
Reassigning to Kevin.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M13
Comment 4•25 years ago
|
||
Updated•25 years ago
|
Whiteboard: [TESTCASE]
Comment 5•25 years ago
|
||
Lifted testcases from spec, wrapped <A> elements around the label text and attached to this bug... It appears that the <LABEL> element is meant to be used in one of two quite different ways, and the first testcase does not apply directly to either of them. The spec at http://www.w3.org/TR/REC-html40/interact/forms.html#h-17.9.1 says (at the end of the section): >When a LABEL element receives focus, it passes the focus on to its >associated control. See the section below on access keys for >examples. This obviously conflicts with the what <A> elements do upon receiving focus. The spec also says (in the same section) that either <LABEL> is used with a "for='someid'" attribute associated with an "id='someid'" attribute of a form control, OR, is used with the label text and the form control as its only contents. Tested, this work correctly by the spec, but incorrectly by expectations that the Anchor elements will work normally. In both forms, clicking on the links made inside the <LABEL> elements does not load the linked page, but flashes the associated form control and then shifts focus to the associated form control (can be verified by typing). The flash happens only the first time, but the change of focus happens on any click to such an anchor. The same result happens with a third form on the testcase that has no Anchors inside the <LABEL> element - this is according to spec. In a fourth form, label text both inside and outside an <A> element passes focus to the associated form control equivalently. * Tested with: 1999-12-09-08-M12 nightly binary on Windows NT 4.0sp3. * Additional Information: Without the fourth form, this bug report looks like it is INVALID, but it may be reasonable to have an <A> inside a <LABEL> work normally so long as there is some other content to act as the label proper. On the other hand, that is complex, and in any case where "<LABEL><A>anchor content</A> label content</LABEL>" may be desired, surely "<A>anchor content</A> <LABEL>label content</LABEL>" could be used.
Comment 6•25 years ago
|
||
Looking at the nsLabelFrame implementation is it will only pass events down to a nsIFormControlFrame. nsLabelFrame::GetFrameForPoint will return the label frame unless it has a child frame with is a nsIFormControlFrame. We need to make the label frame more general.
Updated•25 years ago
|
Target Milestone: M13 → M15
Comment 7•25 years ago
|
||
Moving to M15
Updated•25 years ago
|
Assignee: kmcclusk → rods
Status: ASSIGNED → NEW
Comment 8•25 years ago
|
||
Reassigning to Rod
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Whiteboard: [TESTCASE] → Fix is in my tree
Assignee | ||
Comment 9•25 years ago
|
||
I have the fix
Assignee | ||
Comment 10•25 years ago
|
||
Fixed
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 11•25 years ago
|
||
Re-opening bug and setting severity to critical. Tested on: - MacOS86 2000-01-26-03 Commercial Build - Linux6 2000-01-25-20 Commercial Build - Win98 2000-01-25-20 Commercial Build
Severity: normal → critical
Status: RESOLVED → REOPENED
Comment 13•25 years ago
|
||
Whoops...I think I re-opened prematurely...sorry rods, I just saw the time/datestamp on this bug... Is your fix getting picked up in the 2000-01-27-xx M13 or M14 builds? If you could let me know I'll check out the appropriate build and then close out this bug for you. Thanks and sorry again for blasting through this bug...
Assignee | ||
Comment 14•25 years ago
|
||
It should be fixed in today's M14 build. I checked it in this morning.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Comment 15•25 years ago
|
||
Marking VERIFIED FIXED on: - Linux6 2000-02-01-10 Commercial build - Win98 2000-02-01-08 Commercial build - MacOS86 2000-02-01-09 Commercial build
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•