conversation on layout [was: conversation starters]

Hi math-on-webpages,

Let me try to break this part out.

As you might imagine, I'm interested in discussing layout. Here are some
ideas for a conversation about mathematics using CSS layout:

* examples / use cases
  * see Dani's email calling for example to put on GitHub
* three problems; vertical stacking, enclosures, stretchy characters
  * how is it done today
  * how could it be done in the near future (i.e., using latest standards)
  * what is hard / missing (in even the latest and greatest)

Personally, I'm very interested in identifying low-level issues. For
example, [1] is based off an approach we almost shipped in MathJax for
vertical stretchy constructions (e.g., large braces, parentheses). While it
seems to work, it turned out that it's unreliable when a user changes zoom
levels. It would be nice to use transforms because it drastically reduces
the necessary DOM size. But perhaps transforms are just not meant for this
kind of thing -- which might be worth discussing with CSS WG folks if we
get the chance.

Best regards,
Peter.

[1] http://codepen.io/pkra/pen/PPBWaN


On Wed, May 4, 2016 at 12:16 PM, Peter Krautzberger <
peter.krautzberger@mathjax.org> wrote:

> Hi math-on-webpages,
>
> Here's a short list of topics to start a conversation. These four came up
> on the call, feel free to add.
>
> If you're interested, just
>
> * spin off a new thread (change subject in your reply)
> * comment or +1 so that we can
> * team up for some dedicated conversations
>
> Best regards,
> Peter.
>
> **layout**
>
> Whether CSS, SVG, or canvas, if you're interested in talking about math
> layout on the web, let's collect best practices, use cases, and analyze
> gaps in the OWP.
>
> **accessibility*
>
> If you're working on making math accessible -- ARIA, speech, braille,
> internationalization etc.
>
> **editing**
>
> Web-based editing touches virtually everything -- layout, interaction,
> accessibility -- but gathering information unique to the challenges of
> editing would be worthwhile.
>
> **machine readability**
>
> Exposing information to machines, I hear it's a thing -- JSON, microdata,
> RDFa etc.
>
>