Closed Bug 799927 Opened 13 years ago Closed 13 years ago

Cant access url bar when page has crashed and url bar has been scrolled off screen

Categories

(Firefox OS Graveyard :: Gaia::Browser, defect)

x86
macOS
defect
Not set
normal

Tracking

(blocking-basecamp:-)

RESOLVED INVALID
blocking-basecamp -

People

(Reporter: daleharvey, Unassigned)

Details

Attachments

(1 file)

Attached image Screenshot of problem
As per title If you have not scrolled the page before it crashes then you can access the url bar
blocking-basecamp: --- → ?
Can we get better STR here? Also, can UX create a better outcome for the "Close Tab" button? Pressing "Close Tab" would allow the browser to work, but if there is only one tab open we won't get "Close Tab". Maybe we should, and pressing it will close the crashed tab and open a new about:blank tab.
blocking-basecamp: ? → +
(In reply to Mark Finkle (:mfinkle) from comment #1) > Can we get better STR here? > > Also, can UX create a better outcome for the "Close Tab" button? Pressing > "Close Tab" would allow the browser to work, but if there is only one tab > open we won't get "Close Tab". Maybe we should, and pressing it will close > the crashed tab and open a new about:blank tab. We're actually discussing that in bug 797272. I would like to show about:home if there's only one tab, and it crashes.
There's a workaround to just close the browser app via task manager, and not go back to that page that keeps crashing. Re-nominating.
blocking-basecamp: + → ?
blocking-basecamp: ? → -
I cant remember why accessing the url bar was important, current behaviour is to requirements
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: