[Webkit-unassigned] [Bug 130018] New: Wrong svg in first <object> if you use history back/forward

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Mar 10 05:16:43 PDT 2014


           Summary: Wrong svg in first <object> if you use history
           Product: WebKit
           Version: 420+
          Platform: All
               URL: http://www.networkteam.com/svgProblemVariation/index.h
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: P1
         Component: SVG
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: lars.lehners at networkteam.com
                CC: zimmermann at kde.org

On webpages with more than one svg included (by object tag) we discovered a problem in webkit browsers (like chrome or safari on mac, ios or windows,... maybe on Andoid, too). The problem appears, if you load several pages of a website and after that use the history back button of the browser. If you do so, the content of the first object tag (which should be the first embedded svg) shows other content randomly. Sometimes it works just fine, but sometimes it shows the content of other svg's or even iframes which are embedded into the page. If this happens and you refresh the page everything is fine again. When we analyzed this problem and took a look into the webdeveloper toolbar, we discovered in the DOM:

- The data attribute of the affected object tag points to the correct svg source.
- The dom of the embedded document in the object tag shows what we've already seen: The wrong document
- We've tested that on IE9+ and actual Firefox Browsers, too. Everything works fine here. So we guess it could be a browser bug of webkit browsers? 

Check the attached url to reconstruct the described problem:
1. Open the page in a webkit browser
2. Move at least to 4 pages (pages 1-6). You can use the upper navigation for that
3. After that, use your browsers history back button as often as another logo is shown under the headline "First SVG with fallback"
4. Voilá! There it is :(

We discovered this problem on many different pages, so we can be shure that this is not a side-effect on other feature implementations.

I think this issue is maybe similar to mine: https://bugs.webkit.org/show_bug.cgi?id=106180

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list