Received: by 10.216.136.146 with SMTP id w18mr252401wei.2.1325630358814;
        Tue, 03 Jan 2012 14:39:18 -0800 (PST)
X-BeenThere: trac-dev@googlegroups.com
Received: by 10.180.104.231 with SMTP id gh7ls7862467wib.0.gmail; Tue, 03 Jan
 2012 14:39:16 -0800 (PST)
Received: by 10.227.199.133 with SMTP id es5mr3550954wbb.1.1325630356780;
        Tue, 03 Jan 2012 14:39:16 -0800 (PST)
Received: by 10.227.199.133 with SMTP id es5mr3550953wbb.1.1325630356760;
        Tue, 03 Jan 2012 14:39:16 -0800 (PST)
Return-Path: <christian.b...@free.fr>
Received: from smtp4-g21.free.fr (smtp4-g21.free.fr. [212.27.42.4])
        by gmr-mx.google.com with ESMTP id fw1si37268364wbb.0.2012.01.03.14.39.16;
        Tue, 03 Jan 2012 14:39:16 -0800 (PST)
Received-SPF: pass (google.com: best guess record for domain of christian.b...@free.fr designates 212.27.42.4 as permitted sender) client-ip=212.27.42.4;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of christian.b...@free.fr designates 212.27.42.4 as permitted sender) smtp.mail=christian.b...@free.fr
Received: from [192.168.1.6] (unknown [88.164.127.204])
	by smtp4-g21.free.fr (Postfix) with ESMTP id 841444C802E
	for <trac-dev@googlegroups.com>; Tue,  3 Jan 2012 23:39:12 +0100 (CET)
Message-ID: <4F03838E.8000103@free.fr>
Date: Tue, 03 Jan 2012 23:39:10 +0100
From: Christian Boos <christian.b...@free.fr>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: trac-dev@googlegroups.com
Subject: Re: [Trac-dev] Span macro in Header
References: <5ab95520-ea9d-4869-ba1d-7c5e931c198a@h24g2000yqm.googlegroups.com> <4EA9D092.60804@free.fr>
In-Reply-To: <4EA9D092.60804@free.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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?

-- Christian