From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: reveal.js: duplicate attribute on section and nested h2 cause problem
Date: Wed, 16 Jun 2021 08:05:39 -0400 [thread overview]
Message-ID: <254dafde-1e50-7096-564c-16d4c6082ab1@reagle.org> (raw)
In-Reply-To: <m2sg1i2a9l.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
Thanks, I updated #5965.
I could forsee harm for things that use relative positioning (e.g., move 5 pixels to the left); having it repeated is going to cause problems. I suspect something like this is causing problem with revealjs `r-fit-text`, but I don't understand how it works.
``` js
/**
* Applies JS-dependent layout helpers for the given slide,
* if there are any.
*/
layout( slide ) {
// Autosize text with the r-fit-text class based on the
// size of its container. This needs to happen after the
// slide is visible in order to measure the text.
Array.from( slide.querySelectorAll( '.r-fit-text' ) ).forEach( element => {
fitty( element, {
minSize: 24,
maxSize: this.Reveal.getConfig().height * 0.8,
observeMutations: false,
observeWindow: false
} );
} );
}
```
On 21-06-15 15:33, John MacFarlane wrote:
> See
> https://github.com/jgm/pandoc/issues/5965
> which I'd sort of forgotten about.
>
> "Let's try this for now, where the attributes are the same on headings and divs.
> It seems fairly harmless."
prev parent reply other threads:[~2021-06-16 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 20:07 Joseph Reagle
[not found] ` <e287b684-a708-da7a-21b9-7940a25fcb16-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-06-15 18:35 ` Joseph Reagle
[not found] ` <9d1e996d-0cd0-08e0-5428-e2767995a820-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-06-15 19:33 ` John MacFarlane
[not found] ` <m2sg1i2a9l.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-06-16 12:05 ` Joseph Reagle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=254dafde-1e50-7096-564c-16d4c6082ab1@reagle.org \
--to=joseph.2011-t1oy19wchswdnm+yrofe0a@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).