Skip to content

Move <base> out of drafts #1341

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jul 11, 2024
Merged

Move <base> out of drafts #1341

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions features/draft/html-elements/base.yml → features/base.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,15 @@
draft_date: 2024-06-05
name: <base>
description: The `<base>` element TODO.
description: The `<base>` element sets the base URL (the URL that relative URLs are relative to) for all relative URLs in the document.
spec: https://html.spec.whatwg.org/multipage/semantics.html#the-base-element
group: html
status:
compute_from: html.elements.base
compat_features:
- api.HTMLBaseElement
- api.HTMLBaseElement.href
- api.HTMLBaseElement.target
- html.elements.base
- html.elements.base.href
- html.elements.base.href.forbid_data_javascript_urls
Copy link
Collaborator Author

@ddbeck ddbeck Jul 9, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seeing this in a burndown caused me to include it here.

This is one of many, many behavioral features in BCD that's a bit backwards: the old behavior ought to be a deprecated "feature" that gets removed in a couple of years after everything has settled. This is never something you'd "use" about the feature—rather, it's something that defines what the feature isn't.

For completeness, I've included it, but I'm sorely tempted to create an issue in BCD to start tracking all of these backwards features, so we can eventually flip them around and purge them.

That said, this specific one is new, so I could be persuaded to go flip this one now.

Copy link
Collaborator

@foolip foolip Jul 9, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we just remove behavioral features from all of our burndown tracking? They never have their own MDN pages, so what is anyone ever going to do with the statuses?

Copy link
Collaborator

@foolip foolip Jul 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Meh, ignore my suggestion. Sometimes they'll be useful in compute_from I'm sure, and providing a status for them is harmless.

Copy link
Collaborator Author

@ddbeck ddbeck Jul 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They do get their own pages on caniuse though: https://caniuse.com/mdn-html_elements_base_href_forbid_data_javascript_urls

- html.elements.base.href.relative_url
- html.elements.base.target
25 changes: 25 additions & 0 deletions features/draft/html-elements/base.yml.dist → features/base.yml.dist
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,3 +44,28 @@ compat_features:
- html.elements.base
- html.elements.base.href
- html.elements.base.target

# baseline: high
# baseline_low_date: 2015-07-29
# baseline_high_date: 2018-01-29
# support:
# chrome: "1"
# chrome_android: "18"
# edge: "12"
# firefox: "4"
# firefox_android: "4"
# safari: "3"
# safari_ios: "2"
- html.elements.base.href.relative_url

# baseline: low
# baseline_low_date: 2024-06-11
# support:
# chrome: "58"
# chrome_android: "58"
# edge: "79"
# firefox: "127"
# firefox_android: "127"
# safari: "13.1"
# safari_ios: "13.4"
- html.elements.base.href.forbid_data_javascript_urls