public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Pranesh Prakash <the.solipsist-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: revealjs background and self contained not working anymore
Date: Thu, 7 Oct 2021 21:58:48 -0700 (PDT)	[thread overview]
Message-ID: <f09ffb5b-eff9-451b-aeba-c45b1d456435n@googlegroups.com> (raw)
In-Reply-To: <m2r1d8zl3o.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 3982 bytes --]

For the record, this issue has been fixed upstream, thanks to Christophe 
and Hakim:
https://github.com/fab4100/reveal.js/commit/3e0b68ea80e3c123def3182ecb183febafae8961

On Tuesday, 28 September, 2021 at 10:36:04 pm UTC+5:30 John MacFarlane 
wrote:

>
> Looking at the HTML using the browser's Inspect feature, I
> see that reveal.js is adding a div devoted to backgrounds,
> which uses a background-image-hash attribute. This may be
> constructed improperly for data URIs; anyway, this is one
> thing to investigate here.
>
> John MacFarlane <j...-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> writes:
>
> > Not sure what is happening here, but yes, an issue on the tracker
> > would be welcome.
> >
> > I note also that because the data-background-image attribute
> > is retained on the h1 element as well as being propagated to
> > the section element, we get two copies of the encoded image.
> > That is bad. See also https://github.com/jgm/pandoc/issues/5965
> >
> >
> > christophe dervieux <christoph...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> >
> >> Hello, 
> >>
> >> Here is a reproducible example of the issue
> >>
> >> curl --output background.jpg -L '
> https://unsplash.com/photos/8OyKWQgBsKQ/download?force=true&w=1920'
> >>
> >> echo "# Slide {data-background-image='background.jpg'}" > slide.md
> >> echo "" >> slide.md
> >> echo "Content" >> slide.md
> >>
> >> # Not self contained 
> >> pandoc -t revealjs -s -o slide.html --metadata title="test" slide.md
> >>
> >> # Self contained
> >> pandoc -t revealjs --self-contained -o slide-self-contained.html 
> --metadata title="test" slide.md
> >>
> >> When using self-contained, the background image is no more working. 
> Pandoc 
> >> encodes to data: but it seems reveal.js does not know how to handle it. 
> It 
> >> split the encoded data: in two url component.
> >>
> >> It seems like a change in reveal 4 as using the same slide.md file with 
> >> different version seems to break. 
> >>
> >> What I tried: 
> >>
> >> - Pandoc 2.9.2.1 : last one compatible with reveal.js 3 I believe
> >> 
> >> pandoc.exe -t revealjs --self-contained -o slide-self-contained.html 
> --metadata title="test" -V revealjs-url=https://unpkg.com/reveal.js@3/ 
> slide.md
> >> 
> >> Works as expected 
> >> - Pandoc 2.10: First to use reveal.js 4
> >> 
> >> pandoc.exe -t revealjs --self-contained -o slide-self-contained.html 
> --metadata title="test" -V revealjs-url=https://unpkg.com/reveal.js@4/ 
> slide.md
> >> 
> >> 
> >> So it seems that something broke when upgrading. 
> >>
> >> Is this a known issue ?
> >> Should I open an issue in Pandoc to track ? I believe this could be 
> >> something in reveal.js not handling correctly encoded data: field.
> >>
> >> MANUAL still says (
> >> https://pandoc.org/MANUAL.html#background-in-reveal.js-and-beamer)
> >>
> >> Background images can be added to self-contained reveal.js slideshows 
> and 
> >> to beamer slideshows.
> >>
> >> But maybe self-contained and revealjs does not work well. 
> >>
> >> Thank you
> >> ​
> >>
> >> -- 
> >> 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> >> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pandoc-discuss/80a3d759-3f29-44d8-9a43-5890dcf9b70en%40googlegroups.com
> .
>

-- 
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/f09ffb5b-eff9-451b-aeba-c45b1d456435n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 7085 bytes --]

      parent reply	other threads:[~2021-10-08  4:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28  9:21 christophe dervieux
     [not found] ` <80a3d759-3f29-44d8-9a43-5890dcf9b70en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-28 10:05   ` christophe dervieux
     [not found]     ` <34ae236d-5f4e-42be-8e18-68a5ce5b6f08n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-28 10:06       ` christophe dervieux
2021-09-28 16:04   ` John MacFarlane
     [not found]     ` <m21r581ybt.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-09-28 17:05       ` John MacFarlane
     [not found]         ` <m2r1d8zl3o.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-10-08  4:58           ` Pranesh Prakash [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=f09ffb5b-eff9-451b-aeba-c45b1d456435n@googlegroups.com \
    --to=the.solipsist-re5jqeeqqe8avxtiumwx3w@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).