public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Joseph Reagle
	<joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: reveal.js: duplicate attribute on section and nested h2 cause problem
Date: Tue, 15 Jun 2021 12:33:26 -0700	[thread overview]
Message-ID: <m2sg1i2a9l.fsf@MacBook-Pro-2.hsd1.ca.comcast.net> (raw)
In-Reply-To: <9d1e996d-0cd0-08e0-5428-e2767995a820-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>


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."



Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> writes:

> Anyone have experience with this. Is an attribute on a heading *supposed* to be applied twice on the resulting section *and* heading?
>
> On 21-06-04 16:07, Joseph Reagle wrote:
>> In this [slide][1] you can see that "big text" is pushed off the right side. The [problem][2] is the 'r-fit-text' class attribute on the section element and its child h2. If I remove it from section, the big text works fine -- but not vice versa.
>> 
>> I'm not sure if this is a pandoc or revealjs issue. I just upgraded to revealjs 4.1.1, and I've followed newer  pandocs (now 2.14.0.1) since I last ran these tests.
>> 
>> [1]: https://reagle.org/joseph/talks/2014/exemplar.html#/big-text
>> [2]: https://pandoc.org/try/?text=%23%23+big+text+%7B.r-fit-text%7D%0A&from=markdown&to=revealjs&standalone=0
>> 
>
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/9d1e996d-0cd0-08e0-5428-e2767995a820%40reagle.org.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/m2sg1i2a9l.fsf%40MacBook-Pro-2.hsd1.ca.comcast.net.


  parent reply	other threads:[~2021-06-15 19:33 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 [this message]
     [not found]         ` <m2sg1i2a9l.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-06-16 12:05           ` Joseph Reagle

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=m2sg1i2a9l.fsf@MacBook-Pro-2.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=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).