Do not include the charset in the mimeType for BiDi network.response events
Categories
(Remote Protocol :: WebDriver BiDi, task, P2)
Tracking
(Not tracked)
People
(Reporter: jdescottes, Unassigned)
References
Details
(Whiteboard: [webdriver:backlog])
Attachments
(1 file)
The initial implementation for responseStarted and responseCompleted events include the optional charset in the mimeType property.
This is what the spec PR is currently suggesting, but we realized that CDP is currently only providing the mimeType "essence" (ie "type/subtype")
This was mentioned in the PR https://github.com/w3c/webdriver-bidi/pull/204#discussion_r1067525625
From a consumer point of view, I imagine having a consistent format "type/subtype" makes this information easier to process, so we might update the spec PR in order to match CDP here. If we do, we need to update the implementation accordingly.
Reporter | ||
Updated•2 years ago
|
Reporter | ||
Comment 1•2 years ago
|
||
Depends on D166373
Updated•2 years ago
|
Reporter | ||
Comment 2•2 years ago
|
||
We could also update the wpt server to specify the charset when serving html pages as well.
Or we can use a dedicated handler if we want to test that.
Reporter | ||
Updated•2 years ago
|
Updated•2 years ago
|
Description
•