On Fri, Feb 13, 2015 at 9:02 AM, Glenn Maynard wrote:
> Copying ASCII isn't desirable. It should copy the Unicode string "a →
> b". After all, that's what gets copied if you had done "a →
> b" in the first place.
>
(Oh, I missed the obvious--the "->" from Firefox is coming from the HTML,
of co
Why is it desirable to copy ASCII versions of unicode text? Doesn't most
software now support unicode so the user can copy and paste what they see,
rather than some ASCII-art equivalent?
On 13 February 2015 at 15:45, Boris Zbarsky wrote:
> On 2/13/15 10:15 AM, David Sheets wrote:
>
>> I suppose
On 2/13/15 10:15 AM, David Sheets wrote:
I suppose currently Chrome is preventing copying hidden content but
Firefox is not and neither picks up the CSS content.
Both prevent copying hidden content, but may not have identical
definitions of "hidden".
Neither picks up CSS generated content, b
On Fri, Feb 13, 2015 at 3:02 PM, Glenn Maynard wrote:
> On Fri, Feb 13, 2015 at 5:45 AM, David Sheets wrote:
>>
>> Hello,
>>
>> I have a page with
>>
>> a -> b
>>
>> and style
>>
>> .rarr span { overflow: hidden; height: 0; width: 0; display: inline-block;
>> }
>> .rarr::after { content: "→"; }
>
On Fri, Feb 13, 2015 at 1:08 PM, Nils Dagsson Moskopp
wrote:
> David Sheets writes:
>
>> On Fri, Feb 13, 2015 at 12:18 PM, James M. Greene
>> wrote:
>>> In this case, you can use Unicode escape values by preceding them with a
>>> slash:
>>>
>>> .rarr:after { content: "\2192"; }
>>>
>>>
>>> Thi
On Fri, Feb 13, 2015 at 5:45 AM, David Sheets wrote:
> Hello,
>
> I have a page with
>
> a -> b
>
> and style
>
> .rarr span { overflow: hidden; height: 0; width: 0; display: inline-block;
> }
> .rarr::after { content: "→"; }
>
> (That's RIGHTWARDS ARROW x2192.)
>
> In Firefox 36, this copies and
David Sheets writes:
> On Fri, Feb 13, 2015 at 12:18 PM, James M. Greene
> wrote:
>> In this case, you can use Unicode escape values by preceding them with a
>> slash:
>>
>> .rarr:after { content: "\2192"; }
>>
>>
>> This is specified in the CSS 2.1 spec:
>> http://www.w3.org/TR/CSS2/syndata.h
David Sheets writes:
> On Fri, Feb 13, 2015 at 12:23 PM, Mathias Bynens wrote:
>> On Fri, Feb 13, 2015 at 1:18 PM, James M. Greene
>> wrote:
>>> In this case, you can use Unicode escape values by preceding them with a
>>> slash:
>>
>> OP’s question wasn’t about how to escape non-ASCII character
To expand on my own comment:
> Personally, I would expect and desire the CSS-generated content to be
copied.
...because THAT is what the user sees, per the browser rendering. I'm
surprised that neither Firefox nor Chrome exhibits that behavior.
Sincerely,
James M. Greene
On Feb 13, 2015 6:30
Sorry, David & Mathias. Hasty 6:00am reply here before my brain and eyes
fully woke up!
Interesting question. Personally, I would expect and desire the
CSS-generated content to be copied.
Sincerely,
James M. Greene
On Feb 13, 2015 6:24 AM, "David Sheets" wrote:
> On Fri, Feb 13, 2015 at 12:1
On Fri, Feb 13, 2015 at 12:23 PM, Mathias Bynens wrote:
> On Fri, Feb 13, 2015 at 1:18 PM, James M. Greene
> wrote:
>> In this case, you can use Unicode escape values by preceding them with a
>> slash:
>
> OP’s question wasn’t about how to escape non-ASCII characters, but
> rather about what the
On Fri, Feb 13, 2015 at 12:18 PM, James M. Greene
wrote:
> In this case, you can use Unicode escape values by preceding them with a
> slash:
>
> .rarr:after { content: "\2192"; }
>
>
> This is specified in the CSS 2.1 spec:
> http://www.w3.org/TR/CSS2/syndata.html#characters
>
> Personally, I pr
On Fri, Feb 13, 2015 at 1:18 PM, James M. Greene
wrote:
> In this case, you can use Unicode escape values by preceding them with a
> slash:
OP’s question wasn’t about how to escape non-ASCII characters, but
rather about what the copy/paste behavior should be in browsers.
@David, I don’t think it
In this case, you can use Unicode escape values by preceding them with a
slash:
.rarr:after { content: "\2192"; }
This is specified in the CSS 2.1 spec:
http://www.w3.org/TR/CSS2/syndata.html#characters
Personally, I probably would've just started on StackOverflow with this
question (e.g. [1]
Hello,
I have a page with
a -> b
and style
.rarr span { overflow: hidden; height: 0; width: 0; display: inline-block; }
.rarr::after { content: "→"; }
(That's RIGHTWARDS ARROW x2192.)
In Firefox 36, this copies and pastes like "a -> b" which is the
desired behavior. In Chrome 40, this copies
15 matches
Mail list logo
