Closed Bug 367584 Opened 19 years ago Closed 19 years ago

strange sturcture of itemset

Categories

(Core Graveyard :: XForms, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: surkov, Unassigned)

Details

Generated content for the follwoing itemset <xf:itemset> <xf:item> <xf:label/> </xf:itemset> is <item> <contextcontainer> <item> <label/> </item> </contextcontainer> </item> This doesn't look correctly. I think we shouldn't use nested xf:item elements.
This is the type of thing that we'd catch if we validated the loaded xform against the XForms schema (item cannot be contained inside an itemset). Until we do that, I don't know what the behavior should be. We aren't terribly consistent about it currently.
What elements are allowed to be template content of itemset element? Only xf:item and xf:itemset? Or xf:choices too? Or something else?
<itemset> can have <label>, <value> and <copy> as child elements. @see http://www.w3.org/MarkUp/Forms/2002/XForms-Schema.xsd
(In reply to comment #3) > <itemset> can have <label>, <value> and <copy> as child elements. > @see http://www.w3.org/MarkUp/Forms/2002/XForms-Schema.xsd > So, that is my bad. Just I assume it is the cool thing to use choices and items inside itemset. It's more powerfull than just label, value, copy elements.
Do we still want to leave this bug open or should it be closed? I think that we already have a bug open about validating against/using the xforms schema in our processing (bug 343122)
I see no reason to keep this open, this is either INVALID or WONTFIX, I'd say INVALID. Doesn't really matter.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.