Summary: | [test case] empty iframe covers later div | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Alex Merry <alex.merry> |
Component: | khtml | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | aleksandersen+bugs.kde.org, dsteinbrook, ehamberg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
The JavaScript version
Just the generated HTML |
Description
Alex Merry
2007-02-13 00:30:47 UTC
Created attachment 19654 [details]
The JavaScript version
This is trimmed-down from the original Facebook code. More info displayed when
you open the file. Also, extensive comments in the JavaScript.
Created attachment 19655 [details]
Just the generated HTML
This is just the HTML that the JavaScript generates. You don't get the weird
behaviour of it displaying correctly when you do something with this one. Also
seems to trigger an unrelated bug in the iframe rendering, which makes it
difficult to deal with (the iframe just renders as a blank box sometimes).
Final point: I've seen Bug 31121. All of the testcases on that bug work for me, and the iframe goes underneath the div the second time the script is run, so I don't think it's a duplicate. I can verify this bug. KDE 3.5.6 Kubuntu Feisty It seems to work in KDE4 (SVN). I'll re-open if it re-appears at any point. *** Bug 143655 has been marked as a duplicate of this bug. *** The attached test cases are still valid, but it looks as though Facebook decided to be nice and fix their own code today -- unlike yesterday, all the popup divs are working on the first click now on the site (Konqueror 3.5.6/FreeBSD). I'll reopen this, I just tried test cases with konqueror trunk r654974 and problem is still there. Google is now a perpetrator! They've redesigned their home page (is this the first time ever?), and now the "more" dropdown menu on the top of the page exhibits this behavior (Konqueror/3.5.6). Looking at the source, it is indeed yet another IFRAME within a DIV called my an ONCLICK event. Germain Garand fixed this for 4.0... |