Closed Bug 152582 Opened 22 years ago Closed 7 months ago

XUL templates cannot use variables for predicates

Categories

(Core Graveyard :: RDF, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE
Future

People

(Reporter: nmg, Unassigned)

Details

Attachments

(4 files)

XUL templates which have rule <triple> conditions that match triples and use a variable (bound or unbound) for the predicate behave incorrectly. In the event that the predicate variable has already been bound, the condition matches (i.e. the rule fires) but any other (unbound) variables in that condition are not bound. In the event that the predicate variable is unbound, the condition does not match and the rule does not fire. There's a comment in content/xul/templates/src/nsXULTemplateBuilder.cpp (in the CompileTripleCondition() method) which suggests that this is a known issue and that it may be addressed in the future, but this restriction on the use of <triple> conditions is not made clear in the documentation for XUL templates.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Future
tever is not RDF QA anymore
QA Contact: tever → nobody
waterson left the building
Assignee: waterson → nobody
Status: ASSIGNED → NEW
QA Contact: nobody → core.rdf
Product: Core → Core Graveyard
Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: