[
https://issues.apache.org/jira/browse/OFBIZ-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982644#action_12982644
]
Jacques Le Roux commented on OFBIZ-4120:
----------------------------------------
Adrian, quoting you
{quote}
>From my perspective, as long as OFBiz detects if it is enabled and provides an
>indicator in the rendering context, then we've done our job.
{quote}
Actually that's what I suggestged in the above thread, quoting myself
{quote}
This is user's problem not OFBiz's, we can't take care of all subtilities. But
we should explain this to users. We could add an obivous (colored?) label in
the header (javascript enabled). Then they should be aware and it's their
responsabilites.
{quote}
I will go for that with the jQuery cookie solution and... voilà...
Also I asked
{quote}
BTW I was surprised that Ryan and you put the access to preferences and
languages features in the footer. It's not always visible and seems a bit weird
to me
{quote}
Any answers? ;)
> Umbrella task for features which use javascript to degrade gracefully
> ----------------------------------------------------------------------
>
> Key: OFBIZ-4120
> URL: https://issues.apache.org/jira/browse/OFBIZ-4120
> Project: OFBiz
> Issue Type: Bug
> Components: ALL APPLICATIONS
> Affects Versions: SVN trunk
> Reporter: Jacques Le Roux
> Assignee: Jacques Le Roux
>
> By using more an more javascript we forget sometimes that it may not
> available and OFBiz features should continue to work even it's not as easier
> than wih javascript.
> The 1st thing I'd like to do is also to not depend on the javascripEnabled=Y
> parameter passed from the login URL (it's stored in the session) to determine
> if we use javascrip or not. But to use jQuery cookie plugin to test if we can
> create a cookie, else we know that javascrip is not available
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
