Received: by 10.52.174.114 with SMTP id br18mr8384300vdc.2.1326808593382; Tue, 17 Jan 2012 05:56:33 -0800 (PST) X-BeenThere: trac-dev@googlegroups.com Received: by 10.220.162.207 with SMTP id w15ls5994722vcx.1.gmail; Tue, 17 Jan 2012 05:56:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.94.42 with SMTP id cz10mr1469099vdb.18.1326808591667; Tue, 17 Jan 2012 05:56:31 -0800 (PST) Authentication-Results: ls.google.com; spf=pass (google.com: domain of f.ma...@web.de designates internal as permitted sender) smtp.mail=f.ma...@web.de; dkim=pass header...@web.de Received: by r16g2000yqi.googlegroups.com with HTTP; Tue, 17 Jan 2012 05:56:31 -0800 (PST) Date: Tue, 17 Jan 2012 05:56:31 -0800 (PST) In-Reply-To: <4F03838E.8000103@free.fr> References: <5ab95520-ea9d-4869-ba1d-7c5e931c198a@h24g2000yqm.googlegroups.com> <4EA9D092.60804@free.fr> <4F03838E.8000103@free.fr> User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 6.1; rv:9.0.1) Gecko/20100101 Firefox/9.0.1,gzip(gfe) Message-ID: Subject: Re: Span macro in Header From: Franz To: Trac Development Content-Type: text/plain; charset=ISO-8859-1 Hi, I tried with Trac 0.13dev-r10909 the following Wiki and worked flawlessly (also highlighting in PageOutline-macro): = [[span(Sandbox, style=background-color: yellow)]] = Thanks, Franz On 3 Jan., 23:39, Christian Boos wrote: > On 10/27/2011 11:43 PM, Christian Boos wrote: > > > > > > > > > > > On 10/27/2011 9:27 AM, Franz wrote: > >> Hi, > > >> when I edit some Wiki page or ticket in Trac like this: > >> = The [[span(Sandbox, style=background-color: yellow)]] = > > ... > >> Is this behavior a (known) bug? Or was the span macro not intended for > >> headers? > > > It's a known limitation, yes. ... > > > Ok, so here's a patch that implements this. It also illustrates how a > > macro can sometimes produce inline content, sometimes not (here the > > TicketQueryMacro, producing inline content for the count and compact > > format). In addition, if a macro wants to adapt its generated content to > > the current expected output, it could look at the type of the formatter. > > But in general it should be the other way round: the macro generates > > some content, and the formatter adapts to it. > > Btw, I still have the corresponding patch series aging on my laptop... > and I'd like to commit that. OK? >