See summary, I think "loading" is a better name than "canStop" Let the bike-shedding begin :)
Created attachment 117882 [details] Patch Proposed patch based on summary.
Comment on attachment 117882 [details] Patch LGTM. Perhaps you forgot to ask for a proper review, Michael? Changing flags for the patch.
Comment on attachment 117882 [details] Patch Attachment 117882 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/10689688 New failing tests: svg/custom/linking-uri-01-b.svg
Comment on attachment 117882 [details] Patch This is all in wb2 so the chromium error must be due to flakiness
Comment on attachment 117882 [details] Patch Clearing flags on attachment: 117882 Committed r102035: <http://trac.webkit.org/changeset/102035>
All reviewed patches have been landed. Closing bug.
I was serious about the bike-shedding. We should discuss the options here. It _may_ seem that loading is a better name, but there are also arguments against it. Tor Arne is looking into what we did in Grob and what fits best there. Michael not setting r? was intentional.
(In reply to comment #7) > I was serious about the bike-shedding. We should discuss the options here. It _may_ seem that loading is a better name, but there are also arguments against it. Tor Arne is looking into what we did in Grob and what fits best there. > When I looked at the patch "loading" made way more sense than "canStop". Plus, I remember seeing "loading" as property on other mobile webview APIs before, perhaps on the iOS one, and that also motivated me. > Michael not setting r? was intentional. I'm truly sorry, Simon, I didn't realize it. It was a legitimate mistake. Whatever we decide here, I will make the needed changes.
As part of the API review session at the meeting in Szeged we decided to keep "loading". See also bug #78820 for related changes.