Discussion:
Buttons triggered twice on FireFox.
Benoit VINCENT
2014-05-05 13:45:46 UTC
Permalink
Hi Alain,
Since I have upgraded XSLTForms to r595, I encountered problems with my
triggers (normal appearance) used in Firefox (they work fine with
Chrome). There seems like the DOMactivate event was fired twice.
I searched in your commits and I found you have worked on events
bubbling in r585. In /src/js/xmlevtmngt/Listener.js.xml[87] you test :

event.target.nodeName === "BUTTON"

I think that in Firefox the nodeName is in lower case. So I tried to add :

event.target.nodeName === "BUTTON" || event.target.nodeName ===
"button"

and now, all works correctly with Firefox, miracle !

Is it the good way to correct this bug ?

Thank you for your help,
Benoit
Alain Couthures
2014-05-05 18:22:17 UTC
Permalink
Hi Benoit,

I have not reproduced this issue with latest version of Firefox for
Windows so I would be happy to know more precisely your user environment.

According to HTML specifications, I think that names should always be in
upper case. Anyway, it is quite easy to add .toUpperCase() and it will
be committed in the next build!

Thank you very much!

-Alain
Post by Benoit VINCENT
Hi Alain,
Since I have upgraded XSLTForms to r595, I encountered problems with my
triggers (normal appearance) used in Firefox (they work fine with
Chrome). There seems like the DOMactivate event was fired twice.
I searched in your commits and I found you have worked on events
event.target.nodeName === "BUTTON"
event.target.nodeName === "BUTTON" || event.target.nodeName ===
"button"
and now, all works correctly with Firefox, miracle !
Is it the good way to correct this bug ?
Thank you for your help,
Benoit
------------------------------------------------------------------------------
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Xsltforms-support mailing list
https://lists.sourceforge.net/lists/listinfo/xsltforms-support
Benoit VINCENT
2014-05-06 08:30:50 UTC
Permalink
Hi Alain,
I use the latest release of Firefox on Windows.
I tried to put alert(event.target.nodeName) just before the
event.target.nodeName === "BUTTON" test and I get "BUTTON" with a
smallxforms test and nanoxfserver, but I get "button" with my
application forms. It's the same with Chrome.
The main difference between nanoxfserver and my application is that
the Xsltforms transformation is done server-side in my application. It's
perhaps related to the problem.

Thank's
Benoit
Post by Alain Couthures
Hi Benoit,
I have not reproduced this issue with latest version of Firefox for
Windows so I would be happy to know more precisely your user environment.
According to HTML specifications, I think that names should always be
in upper case. Anyway, it is quite easy to add .toUpperCase() and it
will be committed in the next build!
Thank you very much!
-Alain
Post by Benoit VINCENT
Hi Alain,
Since I have upgraded XSLTForms to r595, I encountered problems with my
triggers (normal appearance) used in Firefox (they work fine with
Chrome). There seems like the DOMactivate event was fired twice.
I searched in your commits and I found you have worked on events
event.target.nodeName === "BUTTON"
event.target.nodeName === "BUTTON" || event.target.nodeName ===
"button"
and now, all works correctly with Firefox, miracle !
Is it the good way to correct this bug ?
Thank you for your help,
Benoit
------------------------------------------------------------------------------
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Xsltforms-support mailing list
https://lists.sourceforge.net/lists/listinfo/xsltforms-support
Continue reading on narkive:
Loading...