mdn / mdn/browser-compat-data

css.properties.resize - Support for replaced elements should be added

Open
#23,314 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browser:multiple data:css good first issue non-required behavior
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Missing compatibility data

What information was incorrect, unhelpful, or incomplete?

The CSS UI spec. says

UAs may also apply it, regardless of the value of the overflow property, to:

  • Replaced elements representing images or videos, such as <img>, <video>, <picture>, <svg>, <object>, or <canvas>.
  • The <iframe> element.

This info is not covered by the compat data yet.

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

Different entries for the elements listed in the spec.

Did you test this? If so, how?

Stumbed over that via https://bugzilla.mozilla.org/show_bug.cgi?id=1280920. I manually checked the test cases there in Firefox 126.0.1 and Chrome 125.0.

Based on that, Chrome supports the property on iframes and Firefox doesn't support it on any of the elements (actually it does, though only when the resource couldn't be loaded and the alternative contents are displayed).

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Web/CSS/resize

MDN metadata
MDN page report details
  • Query: css.properties.resize
  • Report started: 2024-06-09T21:11:07.744Z

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the css.properties.resize entry in the compatibility data and review the CSS UI specification plus the linked Firefox and Chrome reports. Confirm the support details for iframes and the listed replaced elements, then update the data so those element-specific entries are represented and consistent with the observed browser behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.