Noticed while writing a unit test for GTK+ port, after reload only load started is emitted. I'm still not sure if it's a GTK+ specific issue or not, I'll write a unit tests to confirm it.
Ok, so the problem is no that the finished callback is not emitted, but that the resource load callbacks are not emitted because reloading HTML data always loads a blank page in DocumentLoader::maybeLoadEmpty(). Is this known or expected?
As far as I know, we do not remember the source of substitute data. Reloading a page loaded from a string doesn't make sense, but reloading a WebArchive or something loaded from appcache certainly does, and that presumably works. loadHTMLString clients that I know of don't have reload functionality in the first place. What is the scenario where this is needed?
(In reply to comment #2) > As far as I know, we do not remember the source of substitute data. > Reloading a page loaded from a string doesn't make sense, but reloading a > WebArchive or something loaded from appcache certainly does, and that > presumably works. > > loadHTMLString clients that I know of don't have reload functionality in the > first place. What is the scenario where this is needed? I was writing a unit test where loadHTML is very convenient, but I could use loadURL when reload is required. I was not sure if we really wanted it or not, that's why I opened the bug but didn't try to fix it :-)