Closed
Bug 152582
Opened 22 years ago
Closed 7 months ago
XUL templates cannot use variables for predicates
Categories
(Core Graveyard :: RDF, defect)
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.
Reporter | ||
Comment 1•22 years ago
|
||
Reporter | ||
Comment 2•22 years ago
|
||
Reporter | ||
Comment 3•22 years ago
|
||
Reporter | ||
Comment 4•22 years ago
|
||
Updated•22 years ago
|
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Future
Comment 6•21 years ago
|
||
waterson left the building
Assignee: waterson → nobody
Status: ASSIGNED → NEW
QA Contact: nobody → core.rdf
Updated•6 years ago
|
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.
Description
•