Closed
Bug 1453889
Opened 8 years ago
Closed 7 years ago
JS-Confirm message always leads to false in development mobile view
Categories
(DevTools :: Responsive Design Mode, defect)
Tracking
(firefox59 affected, firefox60 affected, firefox61 affected)
RESOLVED
DUPLICATE
of bug 1273997
People
(Reporter: m.gruben, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180412233752
Steps to reproduce:
This is analogue to BUG 1368149.
I build a JavaScript confirm message and expect it to open up at full view and development mobile-view (Ctrl+Shift+M).
The same could be reproduced by typing confirm('hello'); in the js-console.
Actual results:
In full view it works fine. In development mobile-view it immediately returns false right before it opens any modal message.
Expected results:
A confirm-modal should also open up in mobile-view.
Further information: I already restarted Firefox with disabled plug-Ins. Contrary to BUG 1368149 this didnt solve the problem.
![]() |
||
Comment 2•7 years ago
|
||
I have managed to reproduce this issue on the latest FF release (59) and on the latest nightly build (61)
I have tested this by using the console and typing the confirm('hello') command and also using this link "http://gis.pima.gov/plugins/popuptest/jsconfirmtest.htm".
The issue is occurring every time when a JS confirmation message is opened in Responsive Design Mode.
Based on description and the tests executed, I will mark this bug as NEW.
Status: UNCONFIRMED → NEW
status-firefox59:
--- → affected
status-firefox60:
--- → affected
status-firefox61:
--- → affected
Component: Untriaged → Developer Tools: Responsive Design Mode
Ever confirmed: true
Thanks for the report! This is likely the same core issue as bug 1273997, so I'll mark this as duplicate of it.
Please reopen if you believe this is a distinct issue.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•