Skip to content
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

N.A. [HTTP] Enable DefaultURI use for unknown schemes #31100

Closed
1 of 10 tasks
Tracked by #496
Rumyra opened this issue Dec 18, 2023 · 5 comments
Closed
1 of 10 tasks
Tracked by #496

N.A. [HTTP] Enable DefaultURI use for unknown schemes #31100

Rumyra opened this issue Dec 18, 2023 · 5 comments
Assignees

Comments

@Rumyra
Copy link
Collaborator

Rumyra commented Dec 18, 2023

Acceptance Criteria

  • The listed features are documented sufficiently on MDN
  • BCD is updated
  • Interactive example and data repos are updated if appropriate
  • The content has been reviewed as needed

For folks helping with Firefox related documentation

  • Set bugs to dev-doc-complete
  • Add entry to Firefox release notes if feature is enabled in release
  • Add entry to Firefox experimental features page if feature is not yet enabled in release

Related Gecko bugs

https://bugzilla.mozilla.org/show_bug.cgi?id=1603699

Other

  • Check content open issues to see if any pertain to the subject matter. If there are any that can be closed because of the work, do so. If there are any that can be fixed relatively quickly because of the knowledge from completing this issue and you have time, feel free to go ahead and fix them.
  • Check if glossary updates are required for the feature you're documenting - whether an existing term needs to be updated or a new term should be added.
  • Check if BCD update means that content pages need to have experimental markup removed or deprecated markup added (front matter tags and macros).
@github-actions github-actions bot added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Dec 18, 2023
@Rumyra Rumyra removed the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Dec 18, 2023
@hamishwillee hamishwillee self-assigned this Dec 22, 2023
@hamishwillee
Copy link
Collaborator

hamishwillee commented Dec 22, 2023

This has no MDN impact: https://bugzilla.mozilla.org/show_bug.cgi?id=1603699#c13

@hamishwillee hamishwillee changed the title [HTTP] Enable DefaultURI use for unknown schemes N.A. [HTTP] Enable DefaultURI use for unknown schemes Dec 23, 2023
@erosman
Copy link
Contributor

erosman commented Jan 24, 2024

@hamishwillee I was faced with a situation where the absence of information became relevant, in foxyproxy/browser-extension#120 (comment) .
There was no information on Firefox 122 for developers either.

@hamishwillee
Copy link
Collaborator

@erosman Thanks. I asked this question in https://bugzilla.mozilla.org/show_bug.cgi?id=1603699#c13

What is the direct impact of this change to website-developers? What should they do differently because of this?
Can you explain what documents we might need to touch?

Same question to you - what would have made this visible to you? Perhaps an update to add a note to the constructor browser compatibility entry here: https://developer.mozilla.org/en-US/docs/Web/API/URL/URL ?

It could say something like "From version 122 the host and port are parsed for unknown protocols/schemes" ?

@erosman
Copy link
Contributor

erosman commented Jan 26, 2024

It could say something like "From version 122 the host and port are parsed for unknown protocols/schemes" ?

Or maybe... "Prior to version 122, host, hostname, & port were not returned for unknown protocols/schemes."

@hamishwillee
Copy link
Collaborator

hamishwillee commented Jan 28, 2024

Thanks, I like that more. BCD addition here - mdn/browser-compat-data#22079 (made to URL() this is where the URL with non standard schema would be passed in)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

3 participants