I am taking a look at the Release 1 trial version whilst waiting for Release 2  but have come unstuck at the very start.  Firefox tells me javascript is disabled when I try to view any of the examples projects provided or for that matter some simple ones I have created  Note that  they display fine using the builkt in EWB browser  Now javascript is enabled by default when you first install Firefox and I have confirmed  by checking about:config    So why is this not sufficient please and what else do I need to do

Many thanks

Michael Saunders wrote:

> Firefox tells me javascript is disabled

How are you trying to access the examples? Are you entering "localhost"
in the URL bar, or are you loading files directly from disk. Most
browsers will stop the latter working.

--

Matthew Jones

"Matthew Jones" wrote:

Michael Saunders wrote:

> Firefox tells me javascript is disabled

How are you trying to access the examples? Are you entering "localhost"
in the URL bar, or are you loading files directly from disk. Most
browsers will stop the latter working.

--

Matthew Jones

You are correct I missed localhost  What threw me somewhat was that even without localhost I can still open them in IE if I permit the "allow blocked content" prompt  

On 6/3/2015 4:08 AM, Michael Saunders wrote:
> I am taking a look at the Release 1 trial version whilst waiting for Release 2  but have come unstuck at the very start.  Firefox tells me javascript is disabled when I try to view any of the examples projects provided or for that matter some simple ones I have created  Note that  they display fine using the builkt in EWB browser  Now javascript is enabled by default when you first install Firefox and I have confirmed  by checking about:config    So why is this not sufficient please and what else do I need to do

This appears to be a problem with your Firefox setup and not with EWB.
Firefox works fine here (v38.0.5 but has been fine forever).

Do you have plugins/extensions that might block javascript?

What about if you try to access the online samples - do these work ?

Some of them :

http://www.elevatesoft.com:8081/slideshow/slideshow.html

http://www.elevatesoft.com:8081/paint/paint.html

http://www.elevatesoft.com:8081/multimedia/multimedia.html

http://www.elevatesoft.com:8081/databound/databound.html


Raul

This appears to be a problem with your Firefox setup and not with EWB.
Firefox works fine here (v38.0.5 but has been fine forever).

Do you have plugins/extensions that might block javascript?

What about if you try to access the online samples - do these work ?

Some of them :

http://www.elevatesoft.com:8081/slideshow/slideshow.html

http://www.elevatesoft.com:8081/paint/paint.html

http://www.elevatesoft.com:8081/multimedia/multimedia.html

http://www.elevatesoft.com:8081/databound/databound.html

I have no problem with any of these  nor if I prefix localhost before the html file  in question and provided I have EWB open with  the relevant project    Perhaps you can explain why  i need to do this   Is it because the app needs to run over TCP and that using localhost simulates this    And  I thought a web server was only required when working with remote databases  Afraid I am rather ignorant here as I am just starting to look at  web apps
Note that I am accessing these files on my local hard drive


Thanks

Mike

Michael Saunders wrote:

>  if I prefix localhost before the html file  in question and provided
> I have EWB open with  the relevant project    Perhaps you can explain
> why  i need to do this   Is it because the app needs to run over TCP
> and that using localhost simulates this

This is all about security. It is important that the code that the
browser runs comes from the web server that it came from. Files on your
local disk are considered insecure, and since the code may want to call
back to the server to ask for info, the disk file system can't do that.

Key is that you really just need to get used to using localhost (which
means "from the web server on this computer") and then it will be a
good and reliable test.

--

Matthew Jones

On 6/3/2015 12:13 PM, Michael Saunders wrote:
> I have no problem with any of these  nor if I prefix localhost before the html file  in question and provided I have EWB open with  the relevant project    Perhaps you can explain why  i need to do this   Is it because the app needs to run over TCP and that using localhost simulates this    And  I thought a web server was only required when working with remote databases  Afraid I am rather ignorant here as I am just starting to look at  web apps
> Note that I am accessing these files on my local hard drive

Curiously I'm still not able to duplicate the general problem - even
when accessing the ewb app using local file - javascript runs ok still.

What version of Firefox are you using ?

Just to add to what Matthew said the restrictions on running local file
system javascript is getting more and stringent so yes get used to
localhost and local web server.


Raul

Curiously I'm still not able to duplicate the general problem - even
when accessing the ewb app using local file - javascript runs ok still.

What version of Firefox are you using ?

I am using version 38.0.5

What happens is that If I simply click on the html file in windows explorer the following message is displayed in the right hand pane

"JavaScript is not enabled in your web browser, and this application requires JavaScript in order to run properly.  Please enable JavaScript in your browser and reload this page in order to run the application."

Just to add to what Matthew said the restrictions on running local file
system javascript is getting more and stringent so yes get used to
localhost and local web server.




Raul

I think I know what is happening now  The message in windows explorer re Javascript is simply the built in error message in the html file  When I try to launch the html in firefox however I get a blank page  and no javascripot message    However  running with IE confused me because it does display the error message when I try to launch the html file   In fact it appears that Javascript is not the issue  in any case