On Sun, Mar 17, 2013 at 1:40 PM, Robert O'Callahan wrote:
> On Sat, Mar 16, 2013 at 5:52 PM, Gregg Tavares wrote:
>
>> Let me ask again in a different way ;-) Specifically about LCD style
>> antialiasing.
>>
>> What about a context attribute "antialiasRenderingQualityHint" for now
>> with
>> 2 s
On Sat, Mar 16, 2013 at 5:52 PM, Gregg Tavares wrote:
> Let me ask again in a different way ;-) Specifically about LCD style
> antialiasing.
>
> What about a context attribute "antialiasRenderingQualityHint" for now with
> 2 settings "default" and "displayDependent"
>
>context.antialiasRende
On Sun, Mar 17, 2013 at 2:16 AM, Anne van Kesteren wrote:
> On Sun, Mar 17, 2013 at 1:10 AM, Jonas Sicking wrote:
>> On Mon, Mar 11, 2013 at 4:31 AM, Anne van Kesteren wrote:
>>> Preceded the specification? I doubt that. When was it added? The
>>> specification was done start of 2010 somewhere b
On Sun, Mar 17, 2013 at 6:46 AM, Julian Reschke wrote:
> 1) Content-Disposition: inline
>> 2) Content-Disposition: inline; filename="B.txt"
>> 3) Content-Disposition: attachment; filename="B.txt"
>>
>> People generally seem to have a harder time with getting header data
>> right, than getting mark
On 2013-03-17 02:49, Jonas Sicking wrote:
It's currently unclear what to do if a page contains markup like if the resource at audio.wav
responds with either
1) Content-Disposition: inline
2) Content-Disposition: inline; filename="B.txt"
3) Content-Disposition: attachment; filename="B.txt"
Peop
On Sun, Mar 17, 2013 at 1:10 AM, Jonas Sicking wrote:
> On Mon, Mar 11, 2013 at 4:31 AM, Anne van Kesteren wrote:
>> Preceded the specification? I doubt that. When was it added? The
>> specification was done start of 2010 somewhere based on the
>> requirements coming from UMP:
>> http://lists.w3.
