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.

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

Jump to bottom

Agenda for Core Meeting #8

Closed
physikerwelt opened this issue Feb 19, 2019 · 69 comments
Closed

Agenda for Core Meeting #8

physikerwelt opened this issue Feb 19, 2019 · 69 comments
Labels
group admin Tracking agenda and other administrative issues

Comments

@physikerwelt
Copy link
Member

Please add the points you would like to discuss below. Use the following syntax:

- [ ] Topic A #x

where x is the issuenumber of the topic.
@NSoiffer
Copy link
Contributor

NSoiffer commented Feb 20, 2019 •
edited

Topics for 25/2/19 core meeting

@NSoiffer
Copy link
Contributor

NSoiffer commented Feb 25, 2019 •
edited by fred-wang

Topics for 11/3/19 core meeting

@NSoiffer
Copy link
Contributor

NSoiffer commented Mar 12, 2019 •
edited by fred-wang

Topics for 18/3/19 core meeting

@fred-wang
Copy link

fred-wang commented Mar 25, 2019 •
edited

Topics for 01/4/19 core meeting

  1. Decide our workflow and who is in charge of what:
  • Ideas of tasks where people could help: Add a list of ideas for people willing to contribute #82
  • Decide about MathML Core changes (MathML Core subgroup)
  • MathML Core spec changes (Igalia?)
  • WPT tests (Igalia?)
  • Mozilla/WebKit/Chromium heads-up and implementation change (Igalia?)
  • Decide MathML Full spec changes (Core or General meetings?)
  • MathML Full spec changes (?)
  • Write polyfills (?)
  1. Analyze/Discuss result of survey and continue decision about deprecation
  1. BlinkOn/Chromium update (if time permits)
  • Brief summary of status and plan by Igalia
  • Propose list of issues to discuss with at the conference

@davidcarlisle davidcarlisle added the group admin Tracking agenda and other administrative issues label Mar 30, 2019
@NSoiffer
Copy link
Contributor

NSoiffer commented Apr 21, 2019 •
edited by fred-wang

Topics for 22/4/19 core meeting

  • I wasn't at the previous meeting, but from the notes, it appears that the second item above didn't get discussed, so that should get carried forward to this meeting
  • BlinkOn/Chromium conference update/feedback
  • What should polyfills depend on (@briansmith mentioned in Add a list of ideas for people willing to contribute #82 that he is working on a pure CSS polyfill)

-- edit: cancelled due to Easter

@fred-wang
Copy link

fred-wang commented Apr 26, 2019 •
edited

Topics for 29/4/19 core meeting

@NSoiffer
Copy link
Contributor

NSoiffer commented Apr 29, 2019 •
edited by fred-wang

Topics for 6/5/2019 Meeting

@NSoiffer
Copy link
Contributor

NSoiffer commented May 13, 2019 •
edited by fred-wang

Topics for 13/5/19 Meeting

@fred-wang fred-wang mentioned this issue May 16, 2019
Closed
@fred-wang
Copy link

fred-wang commented May 19, 2019 •
edited

Topics for 20/5/19 Meeting

@NSoiffer
Copy link
Contributor

NSoiffer commented May 20, 2019 •
edited by fred-wang

Topics for 3/6/19 Meeting

@fred-wang fred-wang changed the title Agenda for the next meeting Agenda for Core Meeting Jun 3, 2019
@fred-wang fred-wang mentioned this issue Jun 3, 2019
Open
@w3c w3c deleted a comment from NSoiffer Jun 3, 2019
@NSoiffer
Copy link
Contributor

NSoiffer commented Jun 10, 2019 •
edited by fred-wang

Topics for 10/6/19 Meeting

@fred-wang
Copy link

fred-wang commented Jun 12, 2019 •
edited

Topics for 17/6/19 Meeting

@fred-wang
Copy link

fred-wang commented Jun 28, 2019 •
edited

Topics for 01/07/19 Meeting

@fred-wang
Copy link

fred-wang commented Jul 5, 2019 •
edited

Topics for 08/07/19 Meeting

@fred-wang
Copy link

fred-wang commented Jul 10, 2019 •
edited

Topics for 15/07/19 Meeting

@fred-wang
Copy link

fred-wang commented Jul 19, 2019 •
edited

Topics for 22/07/19 Meeting

@NSoiffer
Copy link
Contributor

NSoiffer commented Jul 29, 2019 •
edited

Topics for 29/07/19 Meeting

@NSoiffer
Copy link
Contributor

NSoiffer commented Aug 4, 2019 •
edited by fred-wang

Topics for 05/08/19 Meeting

@fred-wang
Copy link

fred-wang commented Aug 22, 2019 •
edited

Topics for 26/08/19 Meeting

@NSoiffer
Copy link
Contributor

NSoiffer commented Sep 9, 2019 •
edited by fred-wang

Topics for 9/09/19 Meeting

backlog:

@NSoiffer
Copy link
Contributor

NSoiffer commented Sep 12, 2019 •
edited by fred-wang

Topics for 12/09/19 Meeting

@fred-wang
Copy link

fred-wang commented Sep 17, 2019 •
edited by NSoiffer

Topics for 23/09/19 Meeting

backlog:

@fred-wang
Copy link

Topics for 30/09/19 Meeting

backlog:

@fred-wang
Copy link

fred-wang commented Oct 4, 2019 •
edited

Topics for 07/10/19 Meeting

backlog:

@NSoiffer
Copy link
Contributor

NSoiffer commented Oct 14, 2019 •
edited

Topics for 4/11/19 Meeting

backlog:

@NSoiffer
Copy link
Contributor

NSoiffer commented Mar 30, 2020 •
edited

Topics for 6/4/20 Meeting

@NSoiffer
Copy link
Contributor

Topics for 13/4/20 Meeting

@NSoiffer
Copy link
Contributor

NSoiffer commented Apr 20, 2020 •
edited by fred-wang

Topics for 13/4/27 Meeting

@NSoiffer
Copy link
Contributor

NSoiffer commented May 11, 2020 •
edited by fred-wang

Topics for 11/5/20 Meeting

  • Important reminder about our CG's message: Make sure that any feature that goes in browser specifications (including MathML Core, specs from CSS WG, WHATWG's HTML5 spec, specs from ARIA WG) is coordinated with implementers and that they are supportive of the proposal. Implementers include browsers' DOM/rendering/a11y teams and developers of screen readers.

  • Update to operator dictionary:
    https://github.com/mathml-refresh/xml-entities/pulls

@NSoiffer
Copy link
Contributor

NSoiffer commented May 11, 2020 •
edited

Topics for 18/5/20 Meeting

Need resolution for implementation

  • From Rob: The issue is about mroot. The spec says that base and index can only be one child. However last year we experimented with the index consisting of more than one child, and this is the current situation in the internal branch.

Polyfills

@NSoiffer
Copy link
Contributor

NSoiffer commented May 21, 2020 •
edited by fred-wang

Topics for 1/6/20 Meeting

Issues

What goes where

The basic agenda is about what is going to go into the first version of MathML Core.
We have already made a large number of decisions about what is not in core. So we will start with a review of that.

There are several issues open about things that would be good to be in Core but due to time/money/interest are at risk for being in "Core Level 1" (or "Core V1" or ...). We will go over these in the meeting and see whether they really need to be in Level 1, can be pushed to Level 2 (and likely documented as potential level 2 features), or whether they should be pushed all the way back to full for now.

Issues (WIP):

  1. MathML Fundamentals

2.1.7 mathvariant ( https://mathml-refresh.github.io/mathml-core/#the-mathvariant-attribute ).

  • We landed support for "normal" and auto italic. A patche is ready for all of the rest and it does not seem a problem for Google reviewers. The question is on the CSS WG side since there was controversy in the past between doing rendering-only (CSS WG people) and exposing character change (a11y people). For MathML we want the latter for all but the automatic italic on single-char mi. In Chromium/WebKit, text-transform is implemented by character change while it is not in Gecko.

    => Proposal: put this feature "at risk"?

  • Chancery and Spencerian. This is a new proposal and is blocked on Unicode changes and by the previous point.
    Add calligraphic mathvariant support #61

    => Proposal: not in first version of core and remove the issue label?

2.2.3 DOM/JavaScript ( https://mathml-refresh.github.io/mathml-core/#dom-and-javascript ).

  • Allow custom elements in the MathML namespace?
    ( Custom MathML elements #138 )

  • Allow shadow roots of MathML element?
    (https://github.com/mathml-refresh/mathml/issues/140)

    We have interesting experiments in downstream but it will likely be blocked on the WHATWG side for a while and so not upstreamed.

    => Proposal: remove them from the first version? Or define them but put
    "at risk" label?
    => Brian's note: We are taking steps in core informed by these goals. The full goals are not realizable in core v1 all in one step, they should be moved to v2. With v1 in place, they are a considerably more achievable next step

  • Custom layout ( Custom layout as a polyfill option #219)

  • Specialize unknown elements to MathMLUnknownElement?
    (https://github.com/mathml-refresh/mathml/issues/139)

    I think this is mostly useful for custom elements?

    => Proposal: Follow same decision as previous point.
    => Brian's note: This is alignment of the sort that belongs in v1, it would be bad to lose it if we can help it as it helps establish fundamental necessary things for v2 next steps. It basically only aligns us with the web of even a decade and a half ago.

  • HTMLOrSVGElement/ElementCSSInlineStyle

    We definitely want these and they are implemented in all browsers, but
    likely blocked on WHATWG/CSS discussions.

    => Proposal: It seems ok to keep the ISSUE labels.

  • href

    Implemented in WebKit/Gecko and we have a patch for Chromium. However, there are many security questions as well as other issues related to tabindex or shadow DOM. So we are likely not going to upstream the patch for now.

    => Proposal: Put it "at risk"

    => Brian's notes: I think we need this, it seems to make sense to keep for v1 even if it might take some time to achieve parity on this though and can be 'mostly' polyfilled (like actually polyfilled I think) for practical purposes. It definitely would appear to stand in the way of moving some things in v2 forward to me, so just logically it feels like it belongs here.

More OpenType things:

@fred-wang fred-wang added the MathML Core Issues affecting the MathML Core specification label May 22, 2020
@fred-wang
Copy link

fred-wang commented Jun 2, 2020 •
edited by NSoiffer

Topics for 8/6/20 Meeting

  • Interpretation of new display: math/inline-math and compatibility with block/inline ( Interpretation of new display: math/inline-math and compatibility with block/inline #214)

  • href
    Implemented in WebKit/Gecko and we have a patch for Chromium. However, there are many security questions as well as other issues related to tabindex or shadow DOM. So we are likely not going to upstream the patch for now.

    => Proposal: Put it "at risk"

    => Brian's notes: I think we need this, it seems to make sense to keep for v1 even if it might take some time to achieve parity on this though and can be 'mostly' polyfilled (like actually polyfilled I think) for practical purposes. It definitely would appear to stand in the way of moving some things in v2 forward to me, so just logically it feels like it belongs here.

  • mtable/mtr/mtd attr support (#114, mtr columnspan and rowspan mathml-core#44)

More OpenType things:

3.1 Visual formatting model

Issue w3c/mathml-core#175
Should future version of this specification support vertical writing mode?
Issue w3c/mathml-core#127
Should future version of this specification support line breaking?
Issue w3c/mathml-core#120
Should future version of this specification support CSS alignment properties?

A. User Agent Stylesheet
Issue w3c/mathml-core#140
Add rules for text-indent, line-height, word-spacing, letter-spacing?
Issue #36
Add font-style and font-weight on the math root?
Issue w3c/mathml-core#128
Improve rules for href hyperlinks and focusable elements?

@NSoiffer
Copy link
Contributor

NSoiffer commented Jun 8, 2020 •
edited by fred-wang

Topics for 15/6/20 Meeting

  • href (#125)
    [10 minute max discussion]
    Implemented in WebKit/Gecko and we have a patch for Chromium. However, there are many security questions as well as other issues related to tabindex or shadow DOM. So we are likely not going to upstream the patch for now.

    From last week:
    Resolution: BK to bring to TAG the vs limited number of hrefs (compatibility issue).
    Resolution: Discuss this further on Issue 125 and see if we can resolve this (again :-) next week

CSS name bikeshedding

Proposals:

More OpenType things:

3.1 Visual formatting model

Issue w3c/mathml-core#175
Should future version of this specification support vertical writing mode?
Issue w3c/mathml-core#127
Should future version of this specification support line breaking?
Issue w3c/mathml-core#120
Should future version of this specification support CSS alignment properties?

A. User Agent Stylesheet

Issue w3c/mathml-core#140
Add rules for text-indent, line-height, word-spacing, letter-spacing?
Issue #36
Add font-style and font-weight on the math root?
Issue w3c/mathml-core#128
Improve rules for href hyperlinks and focusable elements?

@fred-wang
Copy link

fred-wang commented Jun 16, 2020 •
edited by NSoiffer

Agenda June 22 2020

More OpenType things:

Follow-ons from last week's meeting

3.1 Visual formatting model

Issue w3c/mathml-core#175
Should future version of this specification support vertical writing mode?
Issue w3c/mathml-core#127
Should future version of this specification support line breaking?
Issue w3c/mathml-core#120
Should future version of this specification support CSS alignment properties?

A. User Agent Stylesheet

Issue w3c/mathml-core#140
Add rules for text-indent, line-height, word-spacing, letter-spacing?
Issue #36
Add font-style and font-weight on the math root?
Issue w3c/mathml-core#128
Improve rules for href hyperlinks and focusable elements?

@NSoiffer
Copy link
Contributor

NSoiffer commented Jun 22, 2020 •
edited

Agenda June 29 2020

Brief Status Updates:

  • What's new in Chrome Canary
  • Polyfills

3.1 Visual formatting model

Issue w3c/mathml-core#120
Should future version of this specification support CSS alignment properties?

A. User Agent Stylesheet

Other

@fred-wang
Copy link

Agenda July 06 2020

@NSoiffer
Copy link
Contributor

Agenda July 13 2020

@NSoiffer
Copy link
Contributor

Agenda July 20, 2020

@NSoiffer
Copy link
Contributor

Agenda July 27, 2020

MathML WG charter items

There are 30 MathML Core issues with "needs resolution". Let's try to resolve some of them:

@NSoiffer
Copy link
Contributor

NSoiffer commented Aug 3, 2020

Agenda August 3, 2020

MathML WG charter items

There are 28 MathML Core issues with "needs resolution". Let's try to resolve some of them:

@NSoiffer
Copy link
Contributor

Agenda August 10, 2020

MathML WG charter items

There are 26 MathML Core issues with "needs resolution". Let's try to resolve some of them:

@NSoiffer
Copy link
Contributor

NSoiffer commented Aug 17, 2020 •
edited by rwlbuis

Agenda August 16, 2020

MathML WG charter items

I've "resolved" all but one issue -- anything else before paring it down some and then turning it over to editors to work on the text?

Resolving more issues:

@NSoiffer
Copy link
Contributor

Agenda August 24, 2020

MathML WG charter items

Anything else before paring it down some and then turning it over to editors to work on the text?

Resolving more issues:

@NSoiffer
Copy link
Contributor

NSoiffer commented Aug 24, 2020 •
edited

Agenda August 31, 2020

MathML WG charter items

Volunteers to be Charter Editors?

Decision criteria for what is in core and what isn't

  • How do we decide what goes into core?
  • Does the that decision criteria need to go into the charter somewhere?

Resolving more issues:

@NSoiffer
Copy link
Contributor

Agenda Sept 14, 2020

Implementation updates

CSS updates

Resolving more issues:

@NSoiffer
Copy link
Contributor

Agenda Sept 21, 2020

CSS updates

Resolving more issues:

@NSoiffer
Copy link
Contributor

Agenda Sept 28, 2020

Charter Timelines

Resolving more issues:

@NSoiffer
Copy link
Contributor

NSoiffer commented Oct 5, 2020 •
edited

Agenda Oct 5, 2020

Charter and TPAC

The remaining 'needs resolution' issues:

@NSoiffer
Copy link
Contributor

NSoiffer commented Nov 2, 2020

Agenda Nov 2, 2020

TPAC & Charter

  • Meeting report/feedback
  • Moving the charter forward

Implementation Status Update

  • Chrome
  • Polyfills

The remaining 'needs resolution' issues:

@NSoiffer
Copy link
Contributor

NSoiffer commented Nov 8, 2020 •
edited

Agenda Nov 9, 2020

Status Update

  • Charter
  • Chrome
  • Polyfills

The remaining 'needs resolution' issues:

@fred-wang fred-wang removed the MathML Core Issues affecting the MathML Core specification label Mar 30, 2022
@davidcarlisle
Copy link
Collaborator

core meeings now logged in separate issues, in the mathml-core repo. closing here

@NSoiffer NSoiffer mentioned this issue Jan 30, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
group admin Tracking agenda and other administrative issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@fred-wang @bkardell @davidcarlisle @NSoiffer @physikerwelt