Last Comment Bug 300757 - Implement mustUnderstand attribute
: Implement mustUnderstand attribute
Status: RESOLVED WONTFIX
:
Product: Core Graveyard
Classification: Graveyard
Component: XForms (show other bugs)
: Trunk
: All All
: -- normal (vote)
: ---
Assigned To: xforms
: Stephen Pride
:
Mentors:
http://www.w3.org/TR/xforms/slice3.ht...
Depends on:
Blocks: 299255 326372 326373
  Show dependency treegraph
 
Reported: 2005-07-14 05:22 PDT by Allan Beaufour
Modified: 2016-07-15 14:46 PDT (History)
3 users (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Attachments

Description Allan Beaufour 2005-07-14 05:22:21 PDT
The spec defines a xforms:mustUnderstand attribute that can be placed on _any_
element in _any_ namespace. Argh.

We might need some xtf-like functionality for attributes (possibly also need for
bug 280368).
Comment 1 Allan Beaufour 2006-05-30 02:34:09 PDT
Here's a take on how it could be done: Before sending xforms-ready, we should do a 
document.evaluate("//*[@xf:mustUnderstand = 'true']",
                  document,
                  NSResolver,
                  XPathResult.ANY_TYPE,
                  null);
And then run through all the returned nodes, and figure out whether they are implemented... 

Question is what that means. I wonder if we can ask nsIContent for example whether it has a native implementation or an XBL binding. Maybe just whether it is possible to QI to a given class?
Comment 2 David Bolter [:davidb] 2016-02-04 12:22:43 PST
RIP xforms

Note You need to log in before you can comment on or make changes to this bug.