Closed Bug 1157142 Opened 5 years ago Closed 5 years ago

support 'inline' and 'block' values for the orient attribute in <input type=range>, with 'inline' being the new default behavior

Categories

(Core :: Layout: Form Controls, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
mozilla40
Tracking Status
firefox40 --- fixed

People

(Reporter: jfkthame, Assigned: jfkthame)

References

(Blocks 1 open bug)

Details

Attachments

(2 files, 1 obsolete file)

This will make the 'orient' attribute of <input type=range> similar to the -moz-orient property used by <progress> and <meter> (bug 1028716).

(Actually, 'inline' doesn't need any explicit support; it'll be the unmarked behavior.)

We can support both the logical (inline/block) and physical (horizontal/vertical) values for the attribute by updating forms.css to apply logical styling when the orientation is logically specified, and physical styling when it is physically specified.

This bug does not propose to address the discrepancy between how authors control orientation for <input type=range> (using an HTML attribute) vs the <progress> and <meter> elements (using a CSS property). Because of the desire to style parts of the <input> element in an orientation-aware way, it's not clear how best to handle this. In principle, I think moving <input type=range> to use the CSS property would be desirable, but that would be a more extensive and disruptive change that we should consider separately.
Attachment #8595818 - Attachment is obsolete: true
Attachment #8595818 - Flags: review?(jwatt)
And here are some reftests to check that the new attribute values are behaving as expected.
Attachment #8595988 - Flags: review?(jwatt)
Assignee: nobody → jfkthame
Status: NEW → ASSIGNED
Attachment #8595931 - Flags: review?(jwatt) → review+
Attachment #8595988 - Flags: review?(jwatt) → review+
You need to log in before you can comment on or make changes to this bug.