Open Bug 1797080 Opened 2 years ago Updated 2 years ago

linkedin.com prevents traversing away

Categories

(Core :: DOM: Navigation, defect)

Firefox 108
defect

Tracking

()

UNCONFIRMED

People

(Reporter: Paul.d.fox+bugs, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.0 Safari/605.1.15

Steps to reproduce:

If you visit LinkedIn.com, quite often, when navigating away, LinkedIn.com is reloaded. This includes clicking on a bookmark in the bookmark bar, or typing in the address bar.

Actual results:

linkedin.com persistently shows, even when navigating away.

Expected results:

I do not see this in any other site. I did do some debugging to see what triggers this. This was some time ago when I looked - but the javascript engine is doing something (timer?) that will trigger periodically. Firefox isn't totally shutting down the old page, and allows these timers to re-fire, and cause the page to reload. Whilst I can't recall the exact thing I saw (I can investigate more if you need), but it could be a web socket callback - something that is rarely used on other web sites.

My main fear here, is that if you are subsequently navigating to a sensitve/personal site, you may not realise in time, that your movement didn't take hold, and may end up typing personal details, like passwords in to LinkedIn.com

I have seen this on Linux; I haven't tried to reproduce on Windows or Mac, or mobile.

The Bugbug bot thinks this bug should belong to the 'Firefox::Bookmarks & History' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Bookmarks & History

No - this is not a bookmarks/history issue. It is the closing down of a session as you navigate to a new destination.

Component: Bookmarks & History → Untriaged
Component: Untriaged → DOM: Navigation
Product: Firefox → Core

We probably need a concrete test to move this forward.

Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.