I could see this as an potential add-on for those who wish it, but I
don't think this is a core attribute of a web browser.  From a web
site content development standpoint, those landing pages serve a
purpose (although in most cases, it's because they don't know what
else to do).  Think about the "normal" flow of someone using a site
which requires logging in:

1. Public browsing (news, site updates, etc.)
2. Private login (credential validation)
3. Private important/critical messages (welcome to our site, btw,
we'll be down tomorrow between 2300 and 2359).
4. Private functions (be it e-mail, banking, etc.)
5. Log off (dump security tokens, discard server objects, etc.)
6. Non-critical private/public messages (vendor ads, helpful hints,
site surveys, etc.)  [many times, this would be replaced by just going
back to step 1]

If the browser began jumping around the web, you would effectively
eliminate my last step of the web browsing experience.  This would
force me, as a site developer, to move things like ads, surveys,
notes, which are intended to be afterthoughts of the visit, in to
other steps where they do not belong, or where they could potentially
be obtrusive.  IMHO, the web browser should render what was requested
(even if it is just a boring logout page) and not modify content to
it's liking (redirects are exactly that).

Not to mention, something like this could lead to some server redirect/
security issues; as an addon, it could be disabled if ever
misconfigured, or exploited.  And if you imagine a website who's login
and logout page use the same file: www.somesite.no/auth.xxx, redirects
would fire on login as well, effectively cutting off access to the
site.  To get around this, now you'd have to start tracking history...
browser history coupled with login/logout events and redirections...
no thanks.  :)

--clove


On Oct 26, 12:49 pm, Xakk <[email protected]> wrote:
> The following idea is intended to help keep Chrome in the spirit of
> browser transparency.  The user should not even notice that the
> browser is there; Chrome should be a hardly noticeable means of a
> direct link between a human and the web.  Chrome performs this task
> well except for a few cases that I've noticed.
>
> When a user logs off of a webpage, be it their bank account, email
> account, or other account, he or she is FORCED to interact with the
> browser and choose a new direction.  (The "New Tab" page alleviates
> this problem at the creation of a new tab.)
>
> Wouldn't it be useful if the browser detected a page logout and
> offered some sort of new direction such as redirection to the "New
> Tab" page or some other event.  Perhaps customizable redirects upon
> logout events could be implemented in "Under the Hood" options.
>
> I see this as a useful addition to Chrome's mission, what do you
> think?
>
> Xakk
>
> (cc: Google Chrome Help Forum #Suggestions)
--~--~---------~--~----~------------~-------~--~----~
Chromium Discussion mailing list: [email protected] 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-discuss
-~----------~----~----~----~------~----~------~--~---

Reply via email to