I just had a thought - some of our customers will be using old
browsers. IE6 or suchlike, that don't do HTML5 properly. I thought that
I need to modify the standard index.html page to include something, and
then thought that the smart way to do this is to have a simple link to
a "your browser sucks" page. That way, the main index page can be
unchanging, and I can add new info and updates to the browser.html
page, without changing the EWB application.

And then of course it struck me that this was a thing that EWB 2 could
to even better. The project has a URL for "old browser page" and it
puts that in the index.html, perhaps with a 10 second refresh to take
you there. And it can use it more wisely too, so it can do a Javascript
capability test, and if it isn't good enough, it can redirect there too.

I fail to see a problem with this - one URL, usable in various places,
provides a way for the developer to help those who are on older
browsers.

Thoughts?

Matthew

"Matthew Jones" wrote:

>>I just had a thought - some of our customers will be using old
>>browsers. IE6 or suchlike, that don't do HTML5 properly. I thought that
>>I need to modify the standard index.html page to include something, and
>>then thought that the smart way to do this is to have a simple link to
>>a "your browser sucks" page. That way, the main index page can be
>>unchanging, and I can add new info and updates to the browser.html
>>page, without changing the EWB application.

+1

Although looking at the HTML generated by EWB2 I think that there might be something there already?

Mark Brooks wrote:

> Although looking at the HTML generated by EWB2 I think that there
> might be something there already?

There is a basic message, but I'd like to make it nicer to explain to
people. Don't want to pollute the page with my broken HTML, so a URL
makes it more powerful, allowing a link to anywhere.