Closed
Bug 271724
Opened 20 years ago
Closed 9 years ago
Implement CSS pseudoelements needed for XForms
Categories
(Core Graveyard :: XForms, enhancement)
Core Graveyard
XForms
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: allan, Unassigned)
References
()
Details
Attachments
(1 file)
5.08 KB,
application/xml+xhtml
|
Details |
We need to support the ::value, ::repeat-item, and ::repeat-index pseudoelements.
That will allow styling of f.x. the html:input element in an xforms:input,
without styling the label, etc. For the moment 'xforms|* input' can be used as a
CSS selector to style this, but that is not correct. The most generic and, IMHO,
smart way to do it, would be to let one (re)name the individual items in the
visual content in the XTF elements. Is that possible?
Comment 1•20 years ago
|
||
After implementing this, I think that it should be necessary to change
GetApplyDocumentStyleSheets to return false, in order to disallow this kind of
CSS rules ('xforms|* input') that exposes the element implementation. I am
assuming that retuning false will allow the page author to style the element
using the XForms pseudoelements
Comment 2•20 years ago
|
||
This example can be haired up with ::required et al. after the elements get
moved over to being real pseudo-elements instead of attributes. ::value is the
only one that cannot be emulated using attributes so this test case is for it.
Comment 3•20 years ago
|
||
You mean :required. (A double colon is for pseudo-elements, a single colon is
for pseudo-classes.) Also, the pseudo-element ::value is currently implemented
as an element (and matched as that with CSS), not as an attribute.
Reporter | ||
Updated•19 years ago
|
Assignee: aaronr → xforms
Comment 4•9 years ago
|
||
RIP xforms
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•