Re: JavaScriptEnabled

Le 28/10/2024 à 16:04, Daniel Watford a écrit : I now realise that it is used to detect whether the browser has JavaScript enabled, often conveyed from the browser to the server through a hidden form field. Hi Daniel, Yes that's mostly it indeed. JavaScriptEnabled=Y can also be passed

Re: JavaScriptEnabled

Le 28/10/2024 à 17:17, Michael Brohl a écrit : I generally agree with everything you have described here with one addition: standard functionality should detect that JavaScript is disabled in the browser and render an appropriate message to the user, that activating JavaScript is mandatory.

Re: JavaScriptEnabled

- www.ecomify.de Am 28.10.24 um 16:04 schrieb Daniel Watford: Hi Jacques, Before I could answer your message, I had to spend some time reviewing every location that I could find JavaScriptEnabled in the code to ensure I understood its purpose. I now realise that it is used to detect whether the browser

Re: JavaScriptEnabled

Hi Jacques, Before I could answer your message, I had to spend some time reviewing every location that I could find JavaScriptEnabled in the code to ensure I understood its purpose. I now realise that it is used to detect whether the browser has JavaScript enabled, often conveyed from the

Re: JavaScriptEnabled

Le 27/10/2024 à 13:35, Jacques Le Roux a écrit : Le 26/10/2024 à 13:01, Jacques Le Roux a écrit : Hi, Should we still keep JavaScriptEnabled in soon 2025, and if so why? TIA Jacques Please forget this inappropriate question Jacques Hi, My question was not well expressed, if not cryptic

Re: JavaScriptEnabled

Le 26/10/2024 à 13:01, Jacques Le Roux a écrit : Hi, Should we still keep JavaScriptEnabled in soon 2025, and if so why? TIA Jacques Please forget this inappropriate question Jacques

JavaScriptEnabled

Hi, Should we still keep JavaScriptEnabled in soon 2025, and if so why? TIA Jacques

Re: Keep javaScriptEnabled manage on the framework ?

64311 [http://logos.stannah.co.uk/stan150.jpg] [http://logos.stannah.co.uk/enviro.jpg]Please consider the environment before printing this email. Original message From: Jacques Le Roux Date: 30/08/2017 08:39 (GMT+00:00) To: dev@ofbiz.apache.org Subject: Re: Keep javaScriptEnabled manage o

Re: Keep javaScriptEnabled manage on the framework ?

my refactoring to introduce the common-theme I saw that we currently manage on the framework a variable naming javaScriptEnabled to indicate if a user want or not use the javascipt. This functionality has been introduction by Adrian in 2008 (1) and I not found the origin thread (2) (maybe pre

Re: Keep javaScriptEnabled manage on the framework ?

I saw that we currently manage on the framework a variable naming javaScriptEnabled to indicate if a user want or not use the javascipt. This functionality has been introduction by Adrian in 2008 (1) and I not found the origin thread (2) (maybe pre-apache) Now I didn't see why we kee

Re: Keep javaScriptEnabled manage on the framework ?

OFBIZ-1648 . Cheers Paul Foxworthy On 29 August 2017 at 07:46, Nicolas Malin wrote: Hello, During my refactoring to introduce the common-theme I saw that we currently manage on the framework a variable naming javaScriptEnabled to indicate if a user want or not use the javascipt. This fu

Re: Keep javaScriptEnabled manage on the framework ?

07:46, Nicolas Malin wrote: Hello, During my refactoring to introduce the common-theme I saw that we currently manage on the framework a variable naming javaScriptEnabled to indicate if a user want or not use the javascipt. This functionality has been introduction by Adrian in 2008 (1) and I not

Re: Keep javaScriptEnabled manage on the framework ?

Hi Nicolas, Adrian said something about this in https://issues.apache.org/ jira/browse/OFBIZ-1648 . Cheers Paul Foxworthy On 29 August 2017 at 07:46, Nicolas Malin wrote: Hello, During my refactoring to introduce the common-theme I saw that we currently manage on the framework a variable nam

Re: Keep javaScriptEnabled manage on the framework ?

n 29 August 2017 at 07:46, Nicolas Malin wrote: Hello, During my refactoring to introduce the common-theme I saw that we currently manage on the framework a variable naming javaScriptEnabled to indicate if a user want or not use the javascipt. This functionality has been introduction by Adr

Re: Keep javaScriptEnabled manage on the framework ?

g/ jira/browse/OFBIZ-1648 . Cheers Paul Foxworthy On 29 August 2017 at 07:46, Nicolas Malin wrote: Hello, During my refactoring to introduce the common-theme I saw that we currently manage on the framework a variable naming javaScriptEnabled to indicate if a user want or not use

Re: Keep javaScriptEnabled manage on the framework ?

Nicolas Malin wrote: Hello, During my refactoring to introduce the common-theme I saw that we currently manage on the framework a variable naming javaScriptEnabled to indicate if a user want or not use the javascipt. This functionality has been introduction by Adrian in 2008 (1) and I not found

Re: Keep javaScriptEnabled manage on the framework ?

about this in https://issues.apache.org/ jira/browse/OFBIZ-1648 . Cheers Paul Foxworthy On 29 August 2017 at 07:46, Nicolas Malin wrote: Hello, During my refactoring to introduce the common-theme I saw that we currently manage on the framework a variable naming javaScriptEnabled to indicate if a

Re: Keep javaScriptEnabled manage on the framework ?

y refactoring to introduce the common-theme I saw that we >> currently manage on the framework a variable naming javaScriptEnabled to >> indicate if a user want or not use the javascipt. >> This functionality has been introduction by Adrian in 2008 (1) and I not >> found th

Re: Keep javaScriptEnabled manage on the framework ?

framework a variable naming javaScriptEnabled to > indicate if a user want or not use the javascipt. > This functionality has been introduction by Adrian in 2008 (1) and I not > found the origin thread (2) (maybe pre-apache) > > Now I didn't see why we keep this on the framework

Keep javaScriptEnabled manage on the framework ?

Hello, During my refactoring to introduce the common-theme I saw that we currently manage on the framework a variable naming javaScriptEnabled to indicate if a user want or not use the javascipt. This functionality has been introduction by Adrian in 2008 (1) and I not found the origin thread

Re: JavaScriptEnabled

I'm speaking about http://svn.apache.org/viewvc?rev=1055790&view=rev You may have a look at https://issues.apache.org/jira/browse/OFBIZ-4120 and especially https://issues.apache.org/jira/browse/OFBIZ-4124 if you are really interested Jacques BJ Freeman wrote: If i remember correctly we were

Re: JavaScriptEnabled

Hi Adrian, If you are interested I'm filling https://issues.apache.org/jira/browse/OFBIZ-4120 One thing came into my mind: for security reasons we have heavily introduced use of javascript (see https://issues.apache.org/jira/browse/OFBIZ-2330 and maybe even https://issues.apache.org/jira/brows

Re: JavaScriptEnabled

If i remember correctly we were going to have a tree widget. so I don't see this correct. more it is what people perceive what happen to making ofbiz stand out with its own UI. = BJ Freeman Strategic Power Office with Supplier Automation

Re: JavaScriptEnabled

t saying as long as it's working there is no need to change it. Just because you're having difficulty solving one issue that may or may not have something to with JavaScript doesn't mean we should change things in a way that forces everyone to use it. That's not what I meant. B

Re: JavaScriptEnabled

here is no need to change it. Just because you're having difficulty solving one issue that may or may not have something to with JavaScript doesn't mean we should change things in a way that forces everyone to use it. That's not what I meant. BTW I found the reason it was not workin

Re: JavaScriptEnabled

--- On Sun, 1/16/11, Jacques Le Roux wrote: > From: "Adrian Crum" > > --- On Sun, 1/16/11, Jacques Le Roux > wrote: > >> BTW, what I'd suggest at this stage is to warn the > user > >> that it will miss a lot of things if javascript is > disabled > >> (even if OFBiz > >> should be still barely us

Re: JavaScriptEnabled

From: "Adrian Crum" --- On Sun, 1/16/11, Jacques Le Roux wrote: BTW, what I'd suggest at this stage is to warn the user that it will miss a lot of things if javascript is disabled (even if OFBiz should be still barely usable - not checked, no guarantee...) So, OFBiz was barely usable before

Re: JavaScriptEnabled

x27;s browser setting? -Adrian --- On Sun, 1/16/11, Jacques Le Roux wrote: Hi, What was the intial reason to introduce JavaScriptEnabled? Should we not rather rely on the browser setting to set it in user prefs? Thanks Jacques

Re: JavaScriptEnabled

--- On Sun, 1/16/11, Jacques Le Roux wrote: > BTW, what I'd suggest at this stage is to warn the user > that it will miss a lot of things if javascript is disabled > (even if OFBiz > should be still barely usable - not checked, no > guarantee...) So, OFBiz was barely usable before the JavaScript

Re: JavaScriptEnabled

From: "Jacques Le Roux" From: "Adrian Crum" When the JavaScriptEnabled user setting was introduced, there was no way to determine if the browser had JavaScript enabled. I don't know if that has changed recently. We can use http://plugins.jquery.com/project/Cookie

Re: JavaScriptEnabled

From: "Adrian Crum" When the JavaScriptEnabled user setting was introduced, there was no way to determine if the browser had JavaScript enabled. I don't know if that has changed recently. We can use http://plugins.jquery.com/project/Cookie, it's already embeded in OFBiz.

Re: JavaScriptEnabled

When the JavaScriptEnabled user setting was introduced, there was no way to determine if the browser had JavaScript enabled. I don't know if that has changed recently. The only way to test for JavaScript being enabled is to include a small script in the login screen that add

Re: JavaScriptEnabled

How do we determine the user's browser setting? -Adrian --- On Sun, 1/16/11, Jacques Le Roux wrote: > Hi, > > What was the intial reason to introduce JavaScriptEnabled? > Should we not rather rely on the browser setting to set it > in user prefs? > > Thanks > > Jacques > >

JavaScriptEnabled

Hi, What was the intial reason to introduce JavaScriptEnabled? Should we not rather rely on the browser setting to set it in user prefs? Thanks Jacques