-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
devtools: Use webview_id as browser_id
#35956
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
e90e100 to
eb4e10a
Compare
eb4e10a to
a067dbf
Compare
delan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After working on top of these changes in #35971, I think renaming the fields to webview_id at the serde/struct boundary actually made things more confusing for me, because when dealing with devtools protocol concepts, I expected things to be named after what they’re called in the protocol.
I think it would be better to leave the field names as browser_id, but add doc comments saying they correspond to a webview, and derive the field values from the WebViewId index, just like how outer_window_id values are derived from the PipelineId index. What do you think?
not as confident anymore (see my last comment)
Signed-off-by: atbrakhi <atbrakhi@igalia.com>
Signed-off-by: atbrakhi <atbrakhi@igalia.com>
Signed-off-by: atbrakhi <atbrakhi@igalia.com>
a067dbf to
4f70ef9
Compare
delan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
This PR refactors DevTools to use
webview_idasbrowser_idThese changes do not affect the current behavior of the DevTools in Servo.
./mach build -ddoes not report any errors./mach test-tidydoes not report any errorswebview_idasbrowser_id#35953