Closed Bug 344369 Opened 18 years ago Closed 18 years ago

redesign label to specify control element directly

Categories

(Toolkit :: UI Widgets, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: surkov, Assigned: surkov)

Details

Attachments

(1 file)

Now label uses @control attribute or query nsIDOMXULLabeledControlElement from parent element to determine control element. xforms:label (in xhtml content) underlines accesskey if xforms:label direct child of some control. We need add accesskey underlying for xforms controls in xul context. Here we cannot use @control attribute for these proposes and I guess xforms controls shouldn't implement nsIDOMXULLabeledControlElement.

If xul label will provide a way to specify control element directly then xforms label can be able to use it.
Assignee: jag → surkov.alexander
Component: XP Toolkit/Widgets → XUL Widgets
Product: Core → Toolkit
Attached patch patchSplinter Review
Actually there is the way is to override 'labeledControlElement' property. All I need is xul:label's click handler should use this property too.
Attachment #253484 - Flags: first-review?(enndeakin)
Status: NEW → ASSIGNED
Attachment #253484 - Flags: second-review?(neil)
Comment on attachment 253484 [details] [diff] [review]
patch

looks ok. generally, a second review isn't needed for simple patches like this
Attachment #253484 - Flags: first-review?(enndeakin) → first-review+
Attachment #253484 - Flags: second-review?(neil) → second-review+
Is there a chance to get this patch on 1.8 branch? Who can approve this?
(In reply to comment #3)
>Who can approve this?
1.8 branch drivers, of course, via the approval1.8.1.3 flag.

Attachment #253484 - Flags: approval1.8.1.3?
I doubt it will get approved though, since it is just cleanup that doesn't change any behaviour. Why do you need this in 1.8 when you can just use a workaround?
  
(In reply to comment #5)
> I doubt it will get approved though, since it is just cleanup that doesn't
> change any behaviour. Why do you need this in 1.8 when you can just use a
> workaround?
> 
> 

I like to force xforms:label to use xul:label much more (I assume I will extend xforms label binding from xul:label binding and override 'labeledControlElement' property. So I need this for XForms since they should work on 1.8 and on trunk. What kind of workaround do you see?
Checked in to trunk
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
No longer blocks: 340088
Comment on attachment 253484 [details] [diff] [review]
patch

Clearing approval request since xforms took another approach.
Attachment #253484 - Flags: approval1.8.1.3?
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: