Closed
Bug 299274
Opened 20 years ago
Closed 19 years ago
Invalid 'model=' attribute in form control not processed
Categories
(Core Graveyard :: XForms, defect)
Core Graveyard
XForms
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 280366
People
(Reporter: stpride, Assigned: aaronr)
Details
Attachments
(1 file)
|
888 bytes,
application/xhtml+xml
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050509 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050509 Firefox/1.0.4 If a model="" attribute in a form control points to a non-existent <model>, the processor does not catch the problem. Reproducible: Always
| Reporter | ||
Comment 1•20 years ago
|
||
Comment 2•19 years ago
|
||
The reason it's not throwing an exception is that there's no ref attribute on the input, so we do not actually use it for anything. Adding fx. ref="x" to the input, triggers the exception. Do we really want to support this? It seems like unnecessary work.
Updated•19 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
I agree that it isn't probably ever going to be a problem in the wild and it is taking the spec a little literally, but the testsuite tests for it and Novell, formsPlayer and XSmiles all pass the test.
Comment 4•19 years ago
|
||
(In reply to comment #3) > I agree that it isn't probably ever going to be a problem in the wild and it is > taking the spec a little literally, but the testsuite tests for it and Novell, > formsPlayer and XSmiles all pass the test. Grrr. I'll sent Kevin a flame-mail then ;-)
Comment 5•19 years ago
|
||
This is related to bug 280366, and will probably be fixed there.
Comment 6•19 years ago
|
||
*** This bug has been marked as a duplicate of 280366 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
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
•