Re: Deltaspike fails to detect Javascript in IE8
: Martijn Hiemstra m.hiems...@regas.nl
To: dev@deltaspike.apache.org
Cc:
Sent: Wednesday, 17 July 2013, 14:41
Subject: Re: Deltaspike fails to detect Javascript in IE8
Our clients have found a work around by putting our website in the
list
of
trusted websites.
Will there be a permanent solution? Is it solvable in Deltapike? Or
is
it
perhaps an Internet explorer issue?
Martijn Hiemstra
2013/7/17 it-media.k...@daimler.com
Hello Martijn,
we've had the same issue. This is related to the client window
handling,
that targets modern browsers supporting HTML5.
Simply add a class to your application with the following content:
@Specializes
public class OurClientWindowConfig extends
DefaultClientWindowConfig
{
private static final long serialVersionUID =
-3349441047782577598L;
@Override
public ClientWindowRenderMode getClientWindowRenderMode(final
FacesContext facesContext)
{
return ClientWindowRenderMode.NONE;
}
}
This will remove the client window handling and the messsage should
disappear.
But be aware of the consequences (loss of proper window handling).
Regards,
Heiko
--
-Ursprüngliche Nachricht-
Von: Martijn Hiemstra [mailto:m.hiems...@regas.nl]
Gesendet: Mittwoch, 17. Juli 2013 11:24
An: dev@deltaspike.apache.org
Betreff: Deltaspike fails to detect Javascript in IE8
Hallo Everybody,
We have switched to Deltaspike and ever since when we visit our
website
using IE8 we get the following message:
Your browser does not support JavaScript. Click here to continue
without
JavaScript.
Our browser supports Javascript! All kind of tests prove that.
Since
this
message has started to appear after switching to deltaspike and
the
code
that produces this message is located in deltaspike I decided to
post a
message to this mailing list.
The message is produced in
/deltaspike/modules/jsf/impl/src/main/resources/static/windowhandler.
html
Anybody else noticing this message appearing? We use deltaspike
in
combination with Primefaces 3.5. Any known issues using
deltaspike
with
Primefaces?
Met vriendelijke groet,
Martijn Hiemstra
Java Software Engineer
Regas B.V.
Pelmolenlaan 18a
3447 GW Woerden
If you are not the addressee, please inform us immediately that you
have
received this e-mail by mistake, and delete it. We thank you for
your
support.
Re: Deltaspike fails to detect Javascript in IE8
Hi Martjin,
Actually, we found a very similar issue in our apps at work. We have some
machines w/ IE8, others with IE9 and IE10. For some reason, IE8 was
downgrading to IE7. Found that there was a browser setting causing it to
render all intranet sites in compatibility mode. Thanks MS! We're not
using a JSF front end, instead bootstrap + backbone + lots of other jquery
goodies. As far as i know, this isn't something the app can fix (in fact,
when I tried putting in headers to fix it, I was able to fix it locally but
not when it was running on our QA machines).
John
On Thu, Jul 18, 2013 at 11:51 AM, Martijn Hiemstra m.hiems...@regas.nlwrote:
Hi everybody, Strub,
You mention the following:
In general I'd say that any inhouse application utilizing JFS-2 should have
JavaScript enabled. The non-javascript days are gone - we must get over it
;)
Without JavaScript your app would not work anyway.
That is the issue. We have Javascript enabled. Primefaces with all it's
Javascript worked perfectly together with Myfaces CODI on all browsers even
the older ones. This issue started once we switched to Deltaspike and now
any browser that doesn't support html5 sees the message. In deltaspike
there is a file called windowhandler.html and it's causing the message to
appear. The message appears if the browser doesn't support html5 even when
you have Javascript enabled.
Our clients want to open our website in different tabs to view different
pages at the same time so that they can compare information on the website
so as I understand setting ClientWindowRenderMode.NONE isn't an option?
Perhaps I don't understand how the window handeling works however if we are
using the default settings won't alot of people get this Javascript error
detection? Clients who visit your website will be forced to use the most
modern version of their browser to view the website and that's not always
possible.
Thanks in advance,
Martijn
2013/7/18 Mark Struberg strub...@yahoo.de
Hi Martin!
Heiko already pointed you in the right direction. You can even disable or
tweak the window handling depending on e.g. the UserAgent (we already
exclude bots for example).
Will there be a permanent solution? Is it solvable in Deltapike? Or is
it
perhaps an Internet explorer issue?
In general I'd say that any inhouse application utilizing JFS-2 should
have JavaScript enabled. The non-javascript days are gone - we must get
over it ;)
Without JavaScript your app would not work anyway.
There are basically 3 modes for the window detection.
* none - all browser tab see the same information
* lazy - rewrite the windowId in JavaScript on the target page. Be aware
that the first page hit might trash the beans from your original browser
tab! It works fine if you take care about this in your app design.
* clientwindow - we render a small and fast intermediate page which does
the browser tab detection and then forwards to the destination page.
I did installations where we use the clientwindow mode for all in-house
clients but switch to lazy mode for all public internet usage (based on
the
request IP). We also only enable clientwindow for UserAgents which are
known to support html5 (due to the localstorage trick for getting rid of
the flickering).
LieGrue,
strub
- Original Message -
From: Martijn Hiemstra m.hiems...@regas.nl
To: dev@deltaspike.apache.org
Cc:
Sent: Wednesday, 17 July 2013, 14:41
Subject: Re: Deltaspike fails to detect Javascript in IE8
Our clients have found a work around by putting our website in the list
of
trusted websites.
Will there be a permanent solution? Is it solvable in Deltapike? Or is it
perhaps an Internet explorer issue?
Martijn Hiemstra
2013/7/17 it-media.k...@daimler.com
Hello Martijn,
we've had the same issue. This is related to the client window
handling,
that targets modern browsers supporting HTML5.
Simply add a class to your application with the following content:
@Specializes
public class OurClientWindowConfig extends DefaultClientWindowConfig
{
private static final long serialVersionUID = -3349441047782577598L;
@Override
public ClientWindowRenderMode getClientWindowRenderMode(final
FacesContext facesContext)
{
return ClientWindowRenderMode.NONE;
}
}
This will remove the client window handling and the messsage should
disappear.
But be aware of the consequences (loss of proper window handling).
Regards,
Heiko
--
-Ursprüngliche Nachricht-
Von: Martijn Hiemstra [mailto:m.hiems...@regas.nl]
Gesendet: Mittwoch, 17. Juli 2013 11:24
An: dev@deltaspike.apache.org
Betreff: Deltaspike fails to detect Javascript in IE8
Hallo Everybody,
We have switched to Deltaspike and ever since when we visit our
website
Re: Deltaspike fails to detect Javascript in IE8
John,
meta http-equiv=X-UA-Compatible content=IE=edge always worked for me
so it sounds pretty weird I think but then again it's IE...
Regarding this whole feature and the decisions and configuration one must
do I feel it's a bit tough. I have not read the current docs for this but I
tried it in CODI and felt uncomfortable with it. Good doc + examples are
really needed for a feature like this imo.
cheers
2013/7/18 John D. Ament john.d.am...@gmail.com
Hi Martjin,
Actually, we found a very similar issue in our apps at work. We have some
machines w/ IE8, others with IE9 and IE10. For some reason, IE8 was
downgrading to IE7. Found that there was a browser setting causing it to
render all intranet sites in compatibility mode. Thanks MS! We're not
using a JSF front end, instead bootstrap + backbone + lots of other jquery
goodies. As far as i know, this isn't something the app can fix (in fact,
when I tried putting in headers to fix it, I was able to fix it locally but
not when it was running on our QA machines).
John
On Thu, Jul 18, 2013 at 11:51 AM, Martijn Hiemstra m.hiems...@regas.nl
wrote:
Hi everybody, Strub,
You mention the following:
In general I'd say that any inhouse application utilizing JFS-2 should
have
JavaScript enabled. The non-javascript days are gone - we must get over
it
;)
Without JavaScript your app would not work anyway.
That is the issue. We have Javascript enabled. Primefaces with all it's
Javascript worked perfectly together with Myfaces CODI on all browsers
even
the older ones. This issue started once we switched to Deltaspike and now
any browser that doesn't support html5 sees the message. In deltaspike
there is a file called windowhandler.html and it's causing the message to
appear. The message appears if the browser doesn't support html5 even
when
you have Javascript enabled.
Our clients want to open our website in different tabs to view different
pages at the same time so that they can compare information on the
website
so as I understand setting ClientWindowRenderMode.NONE isn't an option?
Perhaps I don't understand how the window handeling works however if we
are
using the default settings won't alot of people get this Javascript
error
detection? Clients who visit your website will be forced to use the most
modern version of their browser to view the website and that's not always
possible.
Thanks in advance,
Martijn
2013/7/18 Mark Struberg strub...@yahoo.de
Hi Martin!
Heiko already pointed you in the right direction. You can even disable
or
tweak the window handling depending on e.g. the UserAgent (we already
exclude bots for example).
Will there be a permanent solution? Is it solvable in Deltapike? Or
is
it
perhaps an Internet explorer issue?
In general I'd say that any inhouse application utilizing JFS-2 should
have JavaScript enabled. The non-javascript days are gone - we must get
over it ;)
Without JavaScript your app would not work anyway.
There are basically 3 modes for the window detection.
* none - all browser tab see the same information
* lazy - rewrite the windowId in JavaScript on the target page. Be
aware
that the first page hit might trash the beans from your original
browser
tab! It works fine if you take care about this in your app design.
* clientwindow - we render a small and fast intermediate page which
does
the browser tab detection and then forwards to the destination page.
I did installations where we use the clientwindow mode for all in-house
clients but switch to lazy mode for all public internet usage (based on
the
request IP). We also only enable clientwindow for UserAgents which are
known to support html5 (due to the localstorage trick for getting rid
of
the flickering).
LieGrue,
strub
- Original Message -
From: Martijn Hiemstra m.hiems...@regas.nl
To: dev@deltaspike.apache.org
Cc:
Sent: Wednesday, 17 July 2013, 14:41
Subject: Re: Deltaspike fails to detect Javascript in IE8
Our clients have found a work around by putting our website in the list
of
trusted websites.
Will there be a permanent solution? Is it solvable in Deltapike? Or is
it
perhaps an Internet explorer issue?
Martijn Hiemstra
2013/7/17 it-media.k...@daimler.com
Hello Martijn,
we've had the same issue. This is related to the client window
handling,
that targets modern browsers supporting HTML5.
Simply add a class to your application with the following content:
@Specializes
public class OurClientWindowConfig extends DefaultClientWindowConfig
{
private static final long serialVersionUID =
-3349441047782577598L;
@Override
public ClientWindowRenderMode getClientWindowRenderMode(final
FacesContext facesContext
