Open
Bug 1347511
Opened 9 years ago
Updated 3 years ago
RDM clear all body's content
Categories
(DevTools :: Responsive Design Mode, defect, P3)
Tracking
(Not tracked)
REOPENED
People
(Reporter: dehghani.m.c, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(6 files)
Sorry, screenshot for my prev post.
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170313154936
Steps to reproduce:
Open any site, hit Ctrl+Shift+M
Actual results:
RDM mode activated, blank page shows up!
Tired to view page source, but the Url of opened new tab is blank, notice that right-click is disabled, I had to hit Ctrl+U)
BTW I could see the page source using Dev tools, the HTML is:
<html><head></head><body></body></html>
Expected results:
You know this part!
ps:
This happened sometimes, but (for ex.) today I facing this issue 3 times (in about 3 hours), also I found this bug: #1307711, I think it is same as that.
Also I can not refresh the page, I have to close the tab & open the page in new tab.
Do you seen an errors in the Browser Console[1] after this happens?
Can you include info from about:support? Click "copy text to clipboard" and either paste as a comment or add as an attachment.
[1]: https://developer.mozilla.org/en-US/docs/Tools/Browser_Console
Flags: needinfo?(dehghani.m.c)
This sounds like a bad issue, so I'd really like to fix it. Unfortunately, we haven't heard a reply from the reporter, and we're going to need more details here.
Please reopen if you are able to provide more details on the issue.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(dehghani.m.c)
Resolution: --- → INCOMPLETE
I could save Browser Console Data, it happens in FF 53.0.
Notice that this issue kill the browser, I had to close FF from task manager.
I added your requested info. @J. Ryan Stinnett
btw, How I can re-open a bug?!
Flags: needinfo?(jryans)
(In reply to Mehdi from comment #6)
> I added your requested info. @J. Ryan Stinnett
>
> btw, How I can re-open a bug?!
Thanks! I added extra permissions to your Bugzilla account, so you should be able to reopen bugs in the future.
The console log is helpful, but not quite enough to resolve the issue, so I think we'll need a few more things here.
Can you attach the data from about:support? Also, can you try a clean profile to see if it happens there as well?
Status: RESOLVED → REOPENED
Ever confirmed: true
Flags: needinfo?(jryans) → needinfo?(dehghani.m.c)
Resolution: INCOMPLETE → ---
Thank you.
I attached about:support data.
BTW I think the reason of this issue is PrivateTab add-on, I'm not sure, because it doesn't happens all times, I think if I use Firefox for long time (like +3 hour) this will happened.
I try to disable PrivateTab add-on and let you know if it happens again.
Flags: needinfo?(dehghani.m.c)
@Ryan, I'm almost sure that the cause of the issue was PrivateTab add-on, but please don't close the issue, I'll as soon as I was sure enough.
Thank you!
Mehdi, any news here?
Flags: needinfo?(dehghani.m.c)
|
Reporter | |
Comment 11•9 years ago
|
||
Ryan, seems like everything is okay (without PrivateTab add-on), but if is possible, please let this issue be open for 3 or max 4 days, because I'm going to work on new project with lot of JS codes and want to work on mobile view, so I'm working with RDM. if all was good, I'll close this issue as INVALID.
Many thanks.
Flags: needinfo?(dehghani.m.c)
|
|
Reporter | |
Comment 12•9 years ago
|
||
As I didn't face with this issue after I removed PrivateTab add-on, so seems like the problem was the add-on not Firefox itself.
Thanks @Ryan for your time.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → INVALID
|
|
Reporter | |
Comment 13•9 years ago
|
||
Ryan, it happened again in http://detectmobilebrowsers.com/ website. seems like the issue wasn't for PrivateTab add-on. there is a different with first one I faced this issue. now I can close the tab using close button. (I mean now FF response to my action).
|
|
Reporter | |
Comment 14•9 years ago
|
||
I faced the issue again, the attached file contains Browser console log.
(In reply to Mehdi from comment #14)
> Created attachment 8874705 [details]
> browser console log (1347511) .txt
>
> I faced the issue again, the attached file contains Browser console log.
Thanks for including the log. Unfortunately it doesn't appear to include enough info to spot the cause here.
I might need to prepare a special build with extra logging so we can get some idea of what's going wrong here. Would you be open to running a special build of Firefox Nightly?
Flags: needinfo?(dehghani.m.c)
|
|
Reporter | |
Comment 16•9 years ago
|
||
NP, thanks for the support.
Of course, I want to help, just let me know how I can get the special build.
Flags: needinfo?(dehghani.m.c) → needinfo?(jryans)
Okay, I've prepared a logging build: https://treeherder.mozilla.org/#/jobs?repo=try&revision=19aeb8f760364da80b4099f295ce5839ff2c95d8
Assuming you want the Windows 64-bit version, you can download it here:
https://queue.taskcluster.net/v1/task/MUjolvovRMCC7V4RIjFG_A/runs/0/artifacts/public/build/target.zip
Please try to trigger the issue using this build, and then copy the logs from Browser Console once you hit the problem, and attach them here.
It's possible we'll need to try several rounds of this as we learn more about what's wrong. Thanks for your help!
Flags: needinfo?(jryans) → needinfo?(dehghani.m.c)
|
|
Reporter | |
Comment 18•9 years ago
|
||
Here you go. hope this helps.
|
|
Reporter | |
Comment 19•9 years ago
|
||
I'll send more logs, anytime I face the issue.
|
|
Reporter | |
Comment 20•9 years ago
|
||
BTW this time it happens when Dev tools was open.
Flags: needinfo?(dehghani.m.c)
Sorry for the delay here! I've taken a look at the log, but at least from what's logged, it looks as if everything was successful every time.
The logs contain several openings of RDM. Did it only fail the last time?
How do you typically open RDM? Do you open DevTools first and open RDM from within DevTools? Or do you open RDM from the Tools menu / key shortcut when DevTools is closed? (Essentially, is DevTools open or closed when you hit this issue? Or does it not matter?)
Flags: needinfo?(dehghani.m.c)
|
|
Reporter | |
Comment 22•9 years ago
|
||
Don't worry.
Obviously this bug doesn't happens every single time that I open the RDM. last time I browser was open for while, I tired to reproduce the bug on 1 or more opened tab (by frequency toggling RDM), but everything was fine, then I just open new tab, then open Dev tools by hitting F12 and finally hitting Shift+Ctrl+M and bug shows up.
"Did it only fail the last time?" -> Yes
"How do you typically open RDM?" -> using keyboard (Shift+Ctrl+M)
"Is DevTools open or closed when you hit this issue?" -> I can not say that for sure, but last time Dev tools was open. (but you can go with: it doesn't matter, because I think I faced the issue even with closed Dev tools)
The problem is reproducing the bug is impossible by following some steps. I trying to find out how, if I could, I'll let you know.
Last thing:
"The logs contain several openings of RDM." -> there was only one open RDM (several open tabs but I just try to toggle RDM only on one of them, if you mean there is more than one tab open with RDM mode on it)
Flags: needinfo?(dehghani.m.c)
|
|
Reporter | |
Comment 23•8 years ago
|
||
Hi Ryan,
I faced this issue again!, I was working with Inspector, makes some changes on CSS, then I just want to test my changes in Mobile mode, so I opened RDM by hitting Ctrl + Shift + M, result -> the RDM is clear (as you can see in attached screenshot), Firefox doesn't response to any key, etc (just for this tab), Inspector shown prev data (not cleared as before).
I was working for changes for almost 15 minutes, so, when this CRITICAL bug will be fixed?
I just re-installed Firefox 2 days ago. just uBlockOrigin installed (Web extension version), obviously this bug not related to this add-on, because I faced to this issue without any add-on before.
Flags: needinfo?(jryans)
|
|
Reporter | |
Comment 24•8 years ago
|
||
I realize it's quite frustrating to lose work like that. Thanks for your patience so far. If we knew more about what is actually failing here, I would certainly prioritize fixing it! For now, we need to keep working on finding what the problem really is.
I have seen other people mention issues like this in the past, so you are not the only one affected. However, it seems to be quite rare across all Firefox users, or potentially machine specific in some way.
I know you've attached about:support already, but I think some more system details could be helpful here. Could you go to about:telemetry, click on "Environment Data", and copy all of the info into an new attachment (not a comment)?
I think I may need to try to replicate your system as best I can in VM to try to get closer here.
Flags: needinfo?(jryans)
Oh, setting ni? for the environment data I mentioned in comment 25.
Flags: needinfo?(dehghani.m.c)
|
|
Reporter | |
Comment 27•8 years ago
|
||
Here you go bro.
Let me know if you need something else.
Flags: needinfo?(dehghani.m.c) → needinfo?(jryans)
Thanks for sharing this! Your machine seems similar in specs to what I have here...
However, the similar bug 1407830 pushed me to check again on Windows, and I am now able to reproduce fairly well there! (Some months ago, I had checked on Windows as well, but it didn't happen for me at the time.)
Anyway, hopefully this means I have a way to do something here finally. :)
Flags: needinfo?(jryans)
See Also: → 1407830
I think this should now be fixed by bug 1407830.
Mehdi, could you update to Nightly 20171017100127 or later and re-test?
Flags: needinfo?(dehghani.m.c)
See Also: 1307711 →
See Also: 1309631 →
|
|
Reporter | |
Comment 30•8 years ago
|
||
I'll try latest Nightly asap!
Could you please tell me how you could/can reproduce this bug? I'm (one of) reporter(s), but I can not reproduce and I'm curious how I can do that :p
(In reply to Mehdi from comment #30)
> I'll try latest Nightly asap!
>
> Could you please tell me how you could/can reproduce this bug? I'm (one of)
> reporter(s), but I can not reproduce and I'm curious how I can do that :p
It appeared to be timing related, so I would just keep opening and closing RDM until it happened. I don't really have any "magic" steps to force it happen on demand. Sometimes it would take 10 - 20 tries before it would happen, which is a bit exhausting!
Have you noticed it happening at all with Nightly lately?
|
|
Reporter | |
Comment 32•8 years ago
|
||
Thanks for the answer, yes, I faced to the issue in FF 57.x, also latest Nightly [59.0a1 (2017-11-20) (64-bit)]
So, what is next?
Flags: needinfo?(dehghani.m.c) → needinfo?(jryans)
(In reply to Mehdi from comment #32)
> Thanks for the answer, yes, I faced to the issue in FF 57.x, also latest
> Nightly [59.0a1 (2017-11-20) (64-bit)]
>
> So, what is next?
Hmm, so has anything changed at all since you originally reported the bug? Or is it exactly the same as before? Is it less frequent?
Unfortunately, we may be stuck again until I can reproduce what you are seeing. I was so sure we had it solved finally! :(
Flags: needinfo?(jryans) → needinfo?(dehghani.m.c)
|
|
Reporter | |
Comment 34•8 years ago
|
||
> Hmm, so has anything changed at all since you originally reported the bug?
> Or is it exactly the same as before? Is it less frequent?
The only thing I can say is (maybe) the issue is less frequent.
Still body got clear and refresh doesn't work.
Flags: needinfo?(dehghani.m.c)
|
||
Updated•8 years ago
|
Product: Firefox → DevTools
|
||
Updated•7 years ago
|
Priority: -- → P3
|
||
Updated•7 years ago
|
Blocks: rdm-toggle
|
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•