Open Bug 1809854 Opened 2 years ago Updated 2 years ago

Do not include the charset in the mimeType for BiDi network.response events

Categories

(Remote Protocol :: WebDriver BiDi, task, P2)

task
Points:
2

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.

Summary: Do not include the charset in the mimeType → Do not include the charset in the mimeType for BiDi network.response events
Assignee: nobody → jdescottes
Status: NEW → ASSIGNED

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.

Assignee: jdescottes → nobody
Status: ASSIGNED → NEW
Points: --- → 2
Priority: -- → P2
Whiteboard: [webdriver:m6]
Whiteboard: [webdriver:m6] → [webdriver:backlog]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: