... Further, we make the code specifically FOR the "browser UI ".
You wouldnt make a wheel for a car and then say "Well its not my fault if it doesnt bolt on! Its the car designers fault". No, it would be your fault if your specifiacally designed wheel didnt work, and the car manufacturers and users would not use your wheel.


----- Original Message ----- From: "Eugene Kerner" <[email protected]>
To: "Michael M Slusarz" <[email protected]>; <[email protected]>
Sent: Friday, February 19, 2010 10:23 AM
Subject: Re: [imp] Use of Back Button in IMP & Vanishing Left Nav


Uhm,

1. Its done with page cache control rather than counting the number of times js has to hestory minus.
2. Page refreshes dont effect the history.

I realise that the future for the history navigation in web browsers is about to bring change to cater for DHTML/AJAX/etc, but please, there are ways to manage your page navigation and the "too hard basket" as you suggest is not one of them.

Rgds,
Eugene.

----- Original Message ----- From: "Michael M Slusarz" <[email protected]>
To: <[email protected]>
Sent: Friday, February 19, 2010 10:09 AM
Subject: Re: [imp] Use of Back Button in IMP & Vanishing Left Nav


Quoting Eugene Kerner <[email protected]>:

My 2 bobs worth again ...

To my fellow developers out there: "Dont use the back button" is not a solution.

So many websites now are breaking the back button with things like ajax, and then rather than fixing their mistake they are sayiong saying "stuff it the user shouldnt use the back button". But guess what, the user will use the back button, so all you are doing is making your site or application dodgy and unprofessional.
The biggest offender is facebook.

This is an ignorant statement. How is one supposed to fix this? There is absolutely no way to reliably/consistently work around browser UI design, which is inaccessible to anything we can do remotely via code. (We tried capturing back button presses in DIMP 1.x, but it is impossible to catch all cases so it has been removed).

What you are saying is that dynamic refreshing of page elements must not be done, and all page interaction must be accompanied by a total refresh of all page elements. Seems like a gigantic step backwards IMHO.

michael

--
___________________________________
Michael Slusarz [[email protected]]

--
IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]


--
IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]

Reply via email to