Closed
Bug 937702
Opened 11 years ago
Closed 11 years ago
two iframes don't work together
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: pawelcislo, Unassigned)
Details
Attachments
(1 file)
3.58 KB,
application/zip
|
Details |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release)
Build ID: 20131028112446
Steps to reproduce:
I placed two iframes on one page. I used the correct ending tags for both (</iframe>). The first one is in a <div>
Actual results:
Only one of the iframes is displayed and it loses its css formatting and js functions. When I remove the div tags around the first one, the two iframes are displayed, but with the content and formatting of just one! The source is different for each frame, but for whatever reason only content from one of them is displayed in both. What's even more strange, it doesn't matter what order I place them in, it's always one and the same source which is displayed. I don't have this problem in Chrome or Opera.
Expected results:
Both frames should have been displayed (or just the second one, because the first one is set to height 0, which works only if the second iframe is not present in the html). The idea was to load the pronunciation of a verb from one source and the transcription from another. But only the pronunciation site gets loaded in the iframe. In Chrome and Opera this works correctly, the pronunciation iframe is hidden from view by css, the other iframe is displayed at the bottom.
![]() |
||
Comment 1•11 years ago
|
||
> Only one of the iframes is displayed and it loses its css formatting and js functions
Only one is displayed because you explicitly hide the first one in your CSS. And the JS in the iframe that's displayed works fine (or at least the "Translate" button works fine), as far as I can tell.
> In Chrome and Opera this works correctly
I see exactly the same behavior in Chrome and Opera as I do in Firefox... All three show the "Text to Phonetics" iframe and not the "howjsay" iframe.
Flags: needinfo?(pawelcislo)
Reporter | ||
Comment 2•11 years ago
|
||
(In reply to Boris Zbarsky [:bz] from comment #1)
> > Only one of the iframes is displayed and it loses its css formatting and js functions
>
> Only one is displayed because you explicitly hide the first one in your CSS.
> And the JS in the iframe that's displayed works fine (or at least the
> "Translate" button works fine), as far as I can tell.
>
> > In Chrome and Opera this works correctly
>
> I see exactly the same behavior in Chrome and Opera as I do in Firefox...
> All three show the "Text to Phonetics" iframe and not the "howjsay" iframe.
I'm sorry, I didn't specify I use the Linux (Ubuntu) version of Firefox. I've just tried the files on a Windows machine at work, and it indeed works fine here (at least on Firefox 16 which is installed here). On Ubuntu this definitely doesn't work right and the results are different in Chrome and Opera. In Firefox only the howjsay iframe shows up whatever I do to the two iframes.
Flags: needinfo?(pawelcislo)
![]() |
||
Comment 3•11 years ago
|
||
The operating system shouldn't matter here.
Do you see the problem in safe mode? See https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode#w_how-to-start-firefox-in-safe-mode
Reporter | ||
Comment 4•11 years ago
|
||
(In reply to Boris Zbarsky [:bz] from comment #3)
> The operating system shouldn't matter here.
>
> Do you see the problem in safe mode? See
> https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-
> mode#w_how-to-start-firefox-in-safe-mode
Well, it's the weirdest thing. I started to think that it was perhaps the fault of the NoScript addon, which is turned off but has some options enabled in the background and it sometimes causes some problems. So I was going to turn it off completely. But when I turned on my computer today and launched Firefox, it appears to be working correctly (I didn't change anything)! Could it be that yesterday's session was somehow corrupted (I believe I restarted Firefox in the meantime, but I'm not sure)? Anyway, sorry for the trouble, I hope this will be working correctly now.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•