search

jfweemaes / ubiquity-xforms

Automatically exported from code.google.com/p/ubiquity-xforms
0 stars 0 forks source link

DropDown Error in controler.js #519

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Hello everybody!

I found a problem in lib/xforms/controler.js ln 224 / character 4. The 
browsers IE8 and IE7 always advises to this one during loading process. As 
additional information it says "method not supported".

I've got one repeat and a dropdown with change-value-actions.
Other dropdowns just prints "yes" and "no" values.
Both doesn't change their values, after chosing another entry of the 
choises (the "chosen" one stays "<<empty>>").
The repeate doesn't create additional form fileds, every time; But i saw 
the entries will be added after submitting it by POST (+display)

In certain cases everything works well, but after refreshing (F5) again 
the error appears again. 95% of refreshes (+deleting cache, restarting 
browser, etc.) the errors appear.

In FF 3.5.2 the inout fields will not be displayed correctly; the fields 
are like small vertical lines (height of a normal input box; width 
like "0"). IE displayes everything correctly here.

I am running:
Windows XP, IE 8 + FF (Sandbox)
Windows XP, IE 7 + FF (Host)

kind regards

Original issue reported on code.google.com by F.Schroe...@gmail.com on 3 Sep 2009 at 9:48

GoogleCodeExporter commented 8 years ago

Original comment by mark.bir...@gmail.com on 3 Sep 2009 at 11:08

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Hello everybody!

I got the solution to my problem.
Instead of adding the model to the <head> of the document, it needs to be in 
the 
<body>. I get it, by looking for an try on FireFox instdead of IE. The result 
was 
fine: white screen @FireFox 3.5.2 and no errors in IE 7 and 8.

Is't it against the xForms standard to write the model in <body> instead of 
<head>?
If this is the case: what about implementing the same functionality for the 
<head> 
area?

kind regards

Original comment by F.Schroe...@gmail.com on 3 Sep 2009 at 11:41

GoogleCodeExporter commented 8 years ago 
Great...glad you sorted it out.

The XForms spec was changed quite a long time ago so that the xf:model could be 
placed anywhere in the 
document. This was done mainly to make it easier to generate small chunks of 
markup that can be inserted in 
by a CMS, but it helps us because some browsers don't correctly process 
elements in the head.

By the way, the UsingTheLibrary wiki page (http://code.google.com/p/ubiquity-
xforms/wiki/UsingTheLibrary) does mention that the model must be in the body -- 
but I guess we need to 
make that more prominent.

Original comment by mark.bir...@gtempaccount.com on 3 Sep 2009 at 12:10

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Hi there!

I get your page (http://code.google.com/p/ubiquity-
xforms/wiki/UsingTheLibrary) after some time, because i remembered about 
something 
special for FireFox. After that, i started to move the model to the body.
Right now I think that "normaly" the model needs to be in the head (recommended 
by 
W3C). I'll check it's correctnes until tomorrow and notify here.

I agree, that it's important to make it more prominent, that should handle such 
problems better for further purpose.

best regards

Original comment by F.Schroe...@gmail.com on 3 Sep 2009 at 12:21