WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
145505
Add WKTR support for "should open external URLs"
https://bugs.webkit.org/show_bug.cgi?id=145505
Summary
Add WKTR support for "should open external URLs"
Brady Eidson
Reported
2015-05-31 15:45:36 PDT
Add WKTR support for "should open external URLs" This includes: -Adding C-spi, as WKTR still uses that -Adding a "dump policy delegate" call to WKTR -Adding basic tests for the "should open external URLs" support that already exists in the tree
Attachments
Patch v1
(30.63 KB, patch)
2015-05-31 21:32 PDT
,
Brady Eidson
darin
: review+
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Brady Eidson
Comment 1
2015-05-31 21:32:38 PDT
Created
attachment 253988
[details]
Patch v1
Darin Adler
Comment 2
2015-06-01 12:06:16 PDT
Comment on
attachment 253988
[details]
Patch v1 View in context:
https://bugs.webkit.org/attachment.cgi?id=253988&action=review
> Source/WebKit2/WebProcess/InjectedBundle/API/c/WKBundleNavigationActionPrivate.h:35 > +WK_EXPORT bool WKBundleNavigationActionGetShouldOpenExternalURLs(WKBundleNavigationActionRef);
Do we really want to add this just so we can log it? Seems like overkill to me. Isn’t there some other way to verify that the flag is set that is more in line with the feature actually works?
> Source/WebKit2/WebProcess/InjectedBundle/InjectedBundleNavigationAction.h:60 > + bool shouldOpenExternalURLs() const { return m_shouldOpenExternalURLs; } > private:
Strange formatting here. There was a blank line before private before.
Brady Eidson
Comment 3
2015-06-01 12:39:17 PDT
(In reply to
comment #2
)
> Comment on
attachment 253988
[details]
> Patch v1 > > View in context: >
https://bugs.webkit.org/attachment.cgi?id=253988&action=review
> > > Source/WebKit2/WebProcess/InjectedBundle/API/c/WKBundleNavigationActionPrivate.h:35 > > +WK_EXPORT bool WKBundleNavigationActionGetShouldOpenExternalURLs(WKBundleNavigationActionRef); > > Do we really want to add this just so we can log it? Seems like overkill to > me. Isn’t there some other way to verify that the flag is set that is more > in line with the feature actually works?
There's no internal way to verify the feature besides inspecting what is passed to the navigation policy delegate. That said, we didn't really want to expose this feature to the C-SPI at all. Once WKTR moves to Modern WebKit (
https://bugs.webkit.org/show_bug.cgi?id=143743
) this can go away (as the API is exposed much more cleanly there)
> > Source/WebKit2/WebProcess/InjectedBundle/InjectedBundleNavigationAction.h:60 > > + bool shouldOpenExternalURLs() const { return m_shouldOpenExternalURLs; } > > private: > > Strange formatting here. There was a blank line before private before.
Doh! Thanks.
Brady Eidson
Comment 4
2015-06-01 12:57:56 PDT
http://trac.webkit.org/changeset/185072
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug