Ubiquity doesn't appear to work with Firefox.

[GoogleCodeExporter]

> What steps will reproduce the problem?

The attached form is the one I'm working on but I cannot get any examples
to work.

> What is the expected output?

I'd like to see a working XForm like I get from the Mozilla plug-in and
XSLTForms.

> What do you see instead?

The for briefly displays the control values (without showing the controls
themselves) and then all xform controls disappear.

I'm using Windows Vista (Oh how unhappy could I be) FireFox 3.5.2 and
Ubiquity XForms 0.7.0

Original issue reported on code.google.com by philip.fennell on 5 Oct 2009 at 10:38

Attachments:

• ubiquity.html

[GoogleCodeExporter]

Hi Philip, thanks for reporting this.

Because UXF is entirely dependent on the browser eco-system, there are 
unfortunately 
a couple of workarounds required to get your form working.

Firstly, the Firefox HTML parser doesn't recognise empty tags like "<foo />" as 
being 
closed. So it is parsing what you intend to be sibling elements as children, 
nesting 
ever deeper. To work round this requires empty tags to be closed explicitly 
like 
"<foo></foo>". You can read more on this at [1].

Secondly, depending on your browser security settings, there are cross-domain 
issues 
involved in loading the library directly from the Google Code server. If you 
are 
working on your local machine, you may want to do an svn checkout of the 
repository 
[2] and refer to that in your script tag. If you are hosting your forms on a 
web 
server, then you are welcome to host your own copy of the library alongside 
them.

Let me know if these workarounds get you up and running.

Cheers,
Phil.

[1] http://code.google.com/p/ubiquity-xforms/wiki/MarkupMangling
[2] http://code.google.com/p/ubiquity-xforms/source/checkout

Original comment by phil.boo...@gtempaccount.com on 5 Oct 2009 at 12:47

• Changed state: Started
• Added labels: Browser-FF, Iteration-20091002

[GoogleCodeExporter]

Attaching an updated form, with the empty tags closed explicitly.

Original comment by phil.boo...@gtempaccount.com on 5 Oct 2009 at 12:49

Attachments:

• ubiquity.html

[GoogleCodeExporter]

Phil,

Thanks for the info.

I've ensured that all empty tags now have a closing tag and I've checked-out a
read-only copy of the source. I've followed the build instructions and copied 
the
contents of the src build/dist/src directory to my project, I point the script 
src
URI to 'ubiquity-loader.js' using a relative path, but still I get no joy. 
Nothing
happens at all.

I've also tried the forms in build/dist/samples but they show the original 
problem of
all the XForms controls disappearing.

Any ideas?

Original comment by philip.fennell on 5 Oct 2009 at 1:44

[GoogleCodeExporter]

Oh, and I've attached the updated form. 

Original comment by philip.fennell on 5 Oct 2009 at 1:57

Attachments:

• ubiquity.html

[GoogleCodeExporter]

Sorry, yes, there is one more thing that I neglected to mention. In Firefox, if 
you 
want to run forms locally, you will need to unset the strict origin policy for 
'file:' URIs.

To do this, navigate to about:config in the browser and filter the list on 
'strict_orig'. You should see the setting 
'security.fileuri.strict_origin_policy'. 
Toggle that value to false and then restart the browser (there's a bit more 
about 
this at [3]).

That should be the last hoop you need to jump through.

[3] http://code.google.com/p/ubiquity-xforms/wiki/ConfiguringBrowsersForTests

Original comment by phil.boo...@gtempaccount.com on 5 Oct 2009 at 2:11

[GoogleCodeExporter]

So far so good.
Have done the about:config dance I can get the build/dist/samples forms to work.
However, I cannot get my form to work in my project. It will only work if I 
place it
in the build/dist/sample directory and use a relative path of
'../src/ubiquity-loader.js'.

Is this what you'd expect to happen?

Original comment by philip.fennell on 5 Oct 2009 at 2:37

[GoogleCodeExporter]

Definitely not. If a form is working from one location on your machine, then 
I'd expect 
it to work from any other location just as well, assuming that script/@src is 
updated 
correctly of course.

I'll have a little play here to see if I can reproduce.

Original comment by phil.boo...@gtempaccount.com on 5 Oct 2009 at 2:59

[GoogleCodeExporter]

Unfortunately, I've not been able to reproduce the problem from comment #6 at 
all on my 
machine. If it persists, it may be worth your time sending an email to the 
users' list 
[4]. More eyes are likely to see it there, because I'm not sure how closely 
some of the 
other contributors to the project follow the issue tracker.

[4] http://groups.google.com/group/ubiquity-xforms

Original comment by phil.boo...@gtempaccount.com on 6 Oct 2009 at 8:42

• Changed state: Accepted
• Removed labels: Iteration-20091002

[GoogleCodeExporter]

Marking this issue as WontFix, because the original problem appears to have 
been worked 
round successfully. I've raised issue 582 separately to investigate the later 
problem 
(see comment #6).

Original comment by phil.boo...@gtempaccount.com on 6 Oct 2009 at 3:39

• Changed state: WontFix