From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: RFC: Proposal for an Org Special Block for ox-html Date: Thu, 24 May 2018 20:08:09 +0100 Message-ID: <87in7c7tye.fsf@gmail.com> References: <87o9h56jdl.fsf@gmail.com> <87lgc87vf1.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44993) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fLvaz-0001NH-Dn for emacs-orgmode@gnu.org; Thu, 24 May 2018 15:08:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fLvau-0000cI-Um for emacs-orgmode@gnu.org; Thu, 24 May 2018 15:08:17 -0400 Received: from mail-wm0-x232.google.com ([2a00:1450:400c:c09::232]:40231) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fLvau-0000c3-Nz for emacs-orgmode@gnu.org; Thu, 24 May 2018 15:08:12 -0400 Received: by mail-wm0-x232.google.com with SMTP id x2-v6so923713wmh.5 for ; Thu, 24 May 2018 12:08:12 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Kaushal Modi , emacs-org list Hi Kaushal, 2018ko maiatzak 24an, Kaushal Modi-ek idatzi zuen: >=20 > Yes, the proposal though supports these 2 things specific to details > element: >=20 > 1. Detecting "open" attribute via "#+attr_html: open". Is it important for open to be a =E2=80=9Cbare=E2=80=9D attribute (not sure= of the official name) like =E2=80=9C
=E2=80=9D as opposed to =E2=80= =9C
=E2=80=9D? The latter form is already supported (in fact the= second =E2=80=9Copen=E2=80=9D can be any string). Just add #+attr_html: :open any-string-you-want above the block. > > 2. Adding a wrapper

tag around the details portion > following the

tag. Useful if user wants to set CSS rules for > "details .details". The only thing I know off the top of my head is that CSS can be quite hairy, so I would not be surprised if this wrapper is sometimes needed. And indeed, support for it would be missing. Is it something that is likely to crop up for other elements as well, such that it would be desirable to support it in org core? (This is at least partly me wondering out loud, no need to specifically answer unless something particularly occurs to you one way or the other.) --=20 Aaron Ecay