|
|
Posted by Beauregard T. Shagnasty on 08/09/07 18:28
Tim Streater wrote:
> "Beauregard T. Shagnasty" <a.nony.mous@example.invalid> wrote:
>> Tim Streater wrote:
>>> Adrienne Boswell <arbpen@yahoo.com> wrote:
>>>> Javascript should be used as an enhancement. When vital elements
>>>> do not work, then yes, it's time to get rid of the javascript. Do
>>>> something server side.
>>>
>>> Is this a general rule, then?
>>
>> A real rule? Probably not, but would you want to risk losing ~10%
>> of your annual business because visitors couldn't navigate your web
>> site? It's not an actual rule, but it certainly is good common
>> sense, eh?
>
> Well, it depends, doesn't it? The wesbite I manage at work is a front
> end to our assets database. It's used by our engineers, finance,
> development, and operations teams, and by selected engineers of some
> of our customers.
Your description implies that you have access control to this web site,
and that it is not a public site. If so, you can demand that your
engineers et al, have JavaScript enabled. You can even demand that they
all use "Internet Explorer 6 and above" if you wish. <g>
> It wouldn't work worth beans with [without?] extensive use of
> Javascript, PHP, and iframes.
That would be your choice. PHP of course is server-side, and not
dependent upon the visitors' browser. Some people, though not as many as
with JavaScript, may block iframes as well.
Opera: Tools > Preferences > Advanced tab > Content
[ Style Options ] > Display tab
[X] Enable frames
[ ] Enable inline frames
Firefox: URL: about:config
Filter: frame
Change value for: browser.frames.enabled to false
We are saying that an author should not use a technology on a public
site that will render the site useless for a fair chunk of visitors.
--
-bts
-Motorcycles defy gravity; cars just suck
Navigation:
[Reply to this message]
|