GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Define what block percentages resolve against. · Issue #77 · w3c/mathml-core

Define what block percentages resolve against. #77

New issue
Copy link
New issue
Copy link
Open
Open
Define what block percentages resolve against.#77
Copy link
Labels
css/html5need specification updateneeds-tests

Description

@bfgeek
bfgeek
opened on Feb 25, 2019
Issue body actions

https://www.software.hixie.ch/utilities/js/live-dom-viewer/?saved=6703

Safari appears to follow the quirks mode behaviour of walking up ancestor chain.
Firefox appears to resolve against zero.

This needs to be defined, with tests, and various writing modes etc.

Activity

  1. bfgeek commented on Feb 25, 2019

    @bfgeek
    bfgeek
    on Feb 25, 2019
    Author
    More actions

    My preferred mode would be to follow the new grid/flex/layout-api behaviour of not passing parents percent resolution size down to children.

    However this also depends on what is decided for the width/height issue.

  2. fred-wang commented on Jul 5, 2019

    @fred-wang
    fred-wang
    on Jul 5, 2019
    Contributor
    More actions

    I'll put this on the agenda of the next MathML CG meeting.
    See https://github.com/mathml-refresh/mathml/issues/45#issuecomment-508735440

    I think it does not make much sense for math layout to resolve percent size for children as relative to the parent size (unless maybe int table cells?). That complicates things and is likely to be even worse with stretchy operators.

    I see two interpretations possible:
    (1) Like mspace@width and mspace@height in MathML 3: Relative to the default attribute value, which is 0.
    (2) Like mpadded@width and mpadded@height in MathML 3: Relative to the content's size.

    Since mspace content is empty, (2) would also work for mspace.

  3. fred-wang commented on Jul 29, 2019

    @fred-wang
    fred-wang
    on Jul 29, 2019
    Contributor
    More actions

    Consensus during mathml core meeting: Ignore width/height on all new layout as they are no clear use case and that simplifies implementation. It still makes sense for mtable or math elements.

  4. bfgeek commented on Jul 29, 2019

    @bfgeek
    bfgeek
    on Jul 29, 2019
    Author
    More actions

    You still need to define this for nested elements which do abide by width/height. (See test-case).

  5. fred-wang commented on Sep 9, 2019

    @fred-wang
    fred-wang
    on Sep 9, 2019
    Contributor
    More actions

    You still need to define this for nested elements which do abide by width/height. (See test-case).

    Proposal: resolve percent against 0.

  6. NSoiffer commented on Sep 12, 2019

    @NSoiffer
    NSoiffer
    on Sep 12, 2019
    Contributor
    More actions

    This was discussed (argued :-) in the 9/9/19 MathML core meeting. In that meeting, @fred-wang argued for '0' and @NSoiffer argued for the containing block (which could be mtable or math)

    The argument for '0' is simplicity of implementation. The argument for the containing block is consistency with HTML. @rwlbuis was going to look into how hard it really would be to look up and use the containing block's render width/height.

  7. fred-wang commented on Sep 15, 2019

    @fred-wang
    fred-wang
    on Sep 15, 2019
    Contributor
    More actions

    Consensus from 2019/09/12 is essentially: use the size provided by a block container without display: math

  8. davidcarlisle
    transferred this issue fromw3c/mathmlon Jun 30, 2021
  9. davidcarlisle
    added
    css / html5
    need specification update
    need tests
    on Jun 30, 2021
  10. fred-wang
    added
    needs-tests
    and removed
    need tests
    on Jan 18, 2022
  11. fred-wang
    added
    css/html5
    and removed
    css / html5
    on Jul 19, 2023
  12. davidcarlisle commented on Jan 29, 2024

    @davidcarlisle
    davidcarlisle
    on Jan 29, 2024
    Collaborator
    More actions

    Still needs spec change (spec still has issue link note)

  13. moz-wptsync-bot
    added a commit that references this issue on Sep 30, 2024

    Support CSS width/height properties on MathML elements.

    f322877
  14. moz-v2v-gh
    added a commit that references this issue on Sep 30, 2024

    Bug 1916988 - Support CSS width/height properties on MathML elements.…

    656a361
  15. gecko-dev-updater
    added 3 commits that reference this issue on Oct 1, 2024

    Bug 1916988 - Support CSS width/height properties on MathML elements.…

    904e9e0

    Bug 1916988 - Support CSS width/height properties on MathML elements.…

    fc214d3

    Bug 1916988 - Support CSS width/height properties on MathML elements.…

    384bff9
  16. fred-wang
    added a commit that references this issue on Oct 1, 2024

    Support CSS width/height properties on MathML elements. (#48375)

    ee06b94
  17. jamienicol
    added a commit that references this issue on Oct 3, 2024

    Bug 1916988 - Support CSS width/height properties on MathML elements.…

    36dd116
  18. webkit-commit-queue
    added a commit that references this issue on Oct 30, 2024

    Support CSS width/height properties on MathML elements

    83c5b73
  19. jwidar
    added a commit that references this issue on Sep 16, 2025

    Bug 1916988 - Support CSS width/height properties on MathML elements.…

    9c073c7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    css/html5need specification updateneeds-tests

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.