We are happy to announce that the XForms extension for Firefox version 0.8.6 for FF2 is available for download from http://addons.mozilla.org. Please note, we are still waiting for approval for 0.8.6 for FF3 from addons.
Here are the bugs that are fixed in 0.8.6:
412028 valid xsd:date formats being marked invalid 412997 Microseconds not normalized when they need to be 418734 [1.1] Implement XPath function: context() 420224 [1.1] Implement XPath functions: days-to-date and seconds-to-dateTime 421468 [1.1] Support @resource on instance element 422311 [1.1] Implement XPath function is-card-number() 423730 [1.1] Implement XPath function adjust-dateTime-to-timezone 424361 xf:resource only works if it's the first element in xf:submission 426671 [1.1] Implement XPath function digest() 427106 Insert action only inserts first node from origin node-set 427874 now(), local-dateTime() have issues on Mac 428509 Cannot attach JavaScript listeners to XForms events 446368 [1.1] Implement header element for submission
Please let us know if you find any bugs/regressions with this release.
Aaron Reed wrote: > We are happy to announce that the XForms extension for Firefox version > 0.8.6 for FF2 is available for download from http://addons.mozilla.org. > Please note, we are still waiting for approval for 0.8.6 for FF3 from > addons.
> Here are the bugs that are fixed in 0.8.6:
> 412028 valid xsd:date formats being marked invalid > 412997 Microseconds not normalized when they need to be > 418734 [1.1] Implement XPath function: context() > 420224 [1.1] Implement XPath functions: days-to-date and > seconds-to-dateTime > 421468 [1.1] Support @resource on instance element > 422311 [1.1] Implement XPath function is-card-number() > 423730 [1.1] Implement XPath function adjust-dateTime-to-timezone > 424361 xf:resource only works if it's the first element in > xf:submission > 426671 [1.1] Implement XPath function digest() > 427106 Insert action only inserts first node from origin node-set > 427874 now(), local-dateTime() have issues on Mac > 428509 Cannot attach JavaScript listeners to XForms events > 446368 [1.1] Implement header element for submission
> Please let us know if you find any bugs/regressions with this release.
Aaron Reed wrote: > We are happy to announce that the XForms extension for Firefox version > 0.8.6 for FF2 is available for download from http://addons.mozilla.org. > Please note, we are still waiting for approval for 0.8.6 for FF3 from > addons.
As a side note, the Firefox 3 Linux version contains binary parts for x86 and x86_64, so all Linux users who use their distribution's default Firefox installation on 64bit machines should be able to use the addons.mozilla.org version without problems.
Also note that dropdown lists on Linux will have two arrows (bug #457075). The patch provided in the bug is only a kind of a workaround, the "solution" would be to convert the select1 into "native widgets" like this has been done for other elements (but there seems now to be some discussion about whether this was the right thing to do [performance regressions on large data sets due to slow mutation handlers AFAIK], so no idea how this will end up).
Aaron, I could try to put some time into that. If you have a free minute, could you give a quick summary on how it was before you switched to the "native widget approach", what you tried to solve with that and am I right with the performance problems associated with that? I read through some of the bug reports, but the actual intention behind the changes didn't become completely clear to me.
You'd be better off talking to Alex Surkov. He did that work. I don't think that the patch was written in order to have any performance improvements, though we knew that one of the nice results of the patch would be improved performance in some scenarios.
Philipp Wagner wrote: > Aaron Reed wrote: >> We are happy to announce that the XForms extension for Firefox version >> 0.8.6 for FF2 is available for download from http://addons.mozilla.org. >> Please note, we are still waiting for approval for 0.8.6 for FF3 from >> addons.
> As a side note, the Firefox 3 Linux version contains binary parts for > x86 and x86_64, so all Linux users who use their distribution's default > Firefox installation on 64bit machines should be able to use the > addons.mozilla.org version without problems.
> Also note that dropdown lists on Linux will have two arrows (bug > #457075). The patch provided in the bug is only a kind of a workaround, > the "solution" would be to convert the select1 into "native widgets" > like this has been done for other elements (but there seems now to be > some discussion about whether this was the right thing to do > [performance regressions on large data sets due to slow mutation > handlers AFAIK], so no idea how this will end up).
> Aaron, I could try to put some time into that. If you have a free > minute, could you give a quick summary on how it was before you switched > to the "native widget approach", what you tried to solve with that and > am I right with the performance problems associated with that? I read > through some of the bug reports, but the actual intention behind the > changes didn't become completely clear to me.
On Linux, Firefox is unable to locate the XForms XPI from the Tools / Add Ons menu. It works fine from Windows.
1. Start Firefox 3.0.3 on Linux 2. Remove any existing XForms Add-On and restart Firefox if necessary. 3. Select Tools, Addons, Get Addons 4. Type xforms into the search box. 5. Result on Linux is All results are already installed or incompatible _See all results (1)_
Klotz, Leigh wrote: > On Linux, Firefox is unable to locate the XForms XPI from the Tools / > Add Ons menu. > It works fine from Windows.
> 1. Start Firefox 3.0.3 on Linux > 2. Remove any existing XForms Add-On and restart Firefox if necessary. > 3. Select Tools, Addons, Get Addons > 4. Type xforms into the search box. > 5. Result on Linux is > All results are already installed or incompatible > _See all results (1)_
> The Windows experience is different. At step 5 above, you get a search > dialog containing a four-star rated "Add to Firefox" button with a > screenshot.
> I believe some metadata is incorrect, resulting in a false impression > that xforms is not available yet for FF3 on Linux.
> Thank you - this release is greatly appreciated.
> There is an issue on the Mac (OSX.5 FF3.0.3) with the Select1 button. > ...
> The control is functional, but visually confusing. (I can send a > screen shot if that would help.)
give the workaround at #457075 [1] a try.
To try it, go to your extensions folder, from there to {cf2812dc-6a7c-4402-b639-4d277dac4c36}/chrome and unzip the xforms.jar file (it's a simple zip file). Then open the chrome.manifest file, and replace it with the attached one. Go to chrome/content/xforms and replace the xforms.css file with the one attached. Then restart firefox and give it a try: is the problem gone?
> On Linux, Firefox is unable to locate the XForms XPI from the Tools / > Add Ons menu. > It works fine from Windows.
> 1. Start Firefox 3.0.3 on Linux > 2. Remove any existing XForms Add-On and restart Firefox if necessary. > 3. Select Tools, Addons, Get Addons > 4. Type xforms into the search box. > 5. Result on Linux is > All results are already installed or incompatible > _See all results (1)_
> The Windows experience is different. At step 5 above, you get a search > dialog containing a four-star rated "Add to Firefox" button with a > screenshot.
> I believe some metadata is incorrect, resulting in a false impression > that xforms is not available yet for FF3 on Linux.
yes, same problem here. But I would consider this an firefox/addons problem (no idea what they are searching for or returning, AMO uses SSL, so a quick look with wireshark didn't help). So perhaps forward this question to an AMO newsgroup? (I'm currently really short on time, otherwise I'd have done it myself)
On Oct 10, 3:14 am, Philipp Wagner <n...@philipp-wagner.com> wrote:
> give the workaround at #457075 [1] a try. > Then restart firefox and give it a try: is the problem gone?
Thanks Philipp, the patch to the css has removed the native widget. The custom arrow is still (strangely) positioned inside the containing input box with about 1em spacing between the pop-up arrow and the right side of the input.
> On Oct 10, 3:14 am, Philipp Wagner <n...@philipp-wagner.com> wrote:
>> give the workaround at #457075 [1] a try. >> Then restart firefox and give it a try: is the problem gone?
> Thanks Philipp, the patch to the css has removed the native widget. > The custom arrow is still (strangely) positioned inside the containing > input box with about 1em spacing between the pop-up arrow and the > right side of the input.
hm, so while it's less confusing now with only arrow it still needs some more work. Unfortunately, I don't have a Mac so I can do no testing :( I'll try next week to get in contact with Alex Surkov to get some more idea about the real problem behind this, all we're discussing here are workarounds.
A group of us are using the XForms plug-in to develop a project. The new build 0.8.6ff3 now prevents the page from rendering correctly because of the error "Security Error: Content at moz-nullprincipal:{2e9b6847-c3f7-e74e-acfc- ec05914e457a} may not load data from file:///Users..." Which prevents the schema from loading. Other members of our group have the same type of error and our systems range from OSX, Ubuntu, and Windows.
Please open a new thread in this same newsgroup and describe more of exactly your form works. For example, is it loading from the local drive or from a server? Where does the schema live? Stuff like that. If you can provide a small, standalone testcase that exhibits the same problem, that would really help us understand what you are trying to do and what is going on.
> A group of us are using the XForms plug-in to develop a project. The > new build 0.8.6ff3 now prevents the page from rendering correctly > because of the error > "Security Error: Content at moz-nullprincipal:{2e9b6847-c3f7-e74e-acfc- > ec05914e457a} may not load data from file:///Users..." > Which prevents the schema from loading. > Other members of our group have the same type of error and our systems > range from OSX, Ubuntu, and Windows.
> Please open a new thread in this same newsgroup and describe more of > exactly your form works. For example, is it loading from the local > drive or from a server? Where does the schema live? Stuff like that. > If you can provide a small, standalone testcase that exhibits the same > problem, that would really help us understand what you are trying to do > and what is going on.
>> A group of us are using the XForms plug-in to develop a project. The >> new build 0.8.6ff3 now prevents the page from rendering correctly >> because of the error >> "Security Error: Content at moz-nullprincipal:{2e9b6847-c3f7-e74e-acfc- >> ec05914e457a} may not load data from file:///Users..." >> Which prevents the schema from loading. >> Other members of our group have the same type of error and our systems >> range from OSX, Ubuntu, and Windows.
> hm, so while it's less confusing now with only arrow it still needs some > more work. Unfortunately, I don't have a Mac so I can do no testing :( > I'll try next week to get in contact with Alex Surkov to get some more > idea about the real problem behind this, all we're discussing here are > workarounds.
> Philipp
Hi Philipp,
I'm using Mozilla xForms 0.8.6ff3 on Vista and wondering if your workaround above would still apply? I'm having problems with rendering the datepicker widget as it seems the bottom end of the field gets hidden.
Joao wrote: > On Oct 13, 12:57 am, Philipp Wagner <n...@philipp-wagner.com> wrote: >> gspringT...@gmail.com schrieb:
>>> On Oct 13, 9:26 am, Philipp Wagner <n...@philipp-wagner.com> wrote: >>>> could you provide a screenshot somewhere? >>> Please try this >>> http://www.gspring.com.au/select1-custom-popup-1.jpg >> hm, so while it's less confusing now with only arrow it still needs some >> more work. Unfortunately, I don't have a Mac so I can do no testing :( >> I'll try next week to get in contact with Alex Surkov to get some more >> idea about the real problem behind this, all we're discussing here are >> workarounds. > I'm using Mozilla xForms 0.8.6ff3 on Vista and wondering if your > workaround above would still apply? I'm having problems with rendering > the datepicker widget as it seems the bottom end of the field gets > hidden.
It should, I don't remember any commit going into that area of code.
After talking with Alexander I think I know now the real problem behind all this, but didn't get around to have a closer look at the code yet. I think as a first solution it would be best to get the patch to use non-native widgets tidied up and committed. I'll see what I can do.
[mailto:dev-tech-xforms-bounces+joao.c.medeiros=gmail....@lists.mozilla.org] On Behalf Of Philipp Wagner Sent: 27 November 2008 23:30 To: dev-tech-xfo...@lists.mozilla.org Subject: Re: XForms extension for Firefox version 0.8.6 is available
Joao wrote: > On Oct 13, 12:57 am, Philipp Wagner <n...@philipp-wagner.com> wrote: >> gspringT...@gmail.com schrieb:
>>> On Oct 13, 9:26 am, Philipp Wagner <n...@philipp-wagner.com> wrote: >>>> could you provide a screenshot somewhere? >>> Please try this >>> http://www.gspring.com.au/select1-custom-popup-1.jpg >> hm, so while it's less confusing now with only arrow it still needs some >> more work. Unfortunately, I don't have a Mac so I can do no testing :( >> I'll try next week to get in contact with Alex Surkov to get some more >> idea about the real problem behind this, all we're discussing here are >> workarounds. > I'm using Mozilla xForms 0.8.6ff3 on Vista and wondering if your > workaround above would still apply? I'm having problems with rendering > the datepicker widget as it seems the bottom end of the field gets > hidden.
It should, I don't remember any commit going into that area of code.
After talking with Alexander I think I know now the real problem behind all this, but didn't get around to have a closer look at the code yet. I think as a first solution it would be best to get the patch to use non-native widgets tidied up and committed. I'll see what I can do.
|
