On 18 Jun 2015, at 13:07, Jonny Rein Eriksen jon...@opera.com wrote:
On 18.06.2015 12:01, Florian Rivoal wrote:
Would it make sense to add an 'auto' value to the lang attribute, explicitly
instructing the UA to try and guess what language is being entered?
Remembering what was used last
Hello all:
On language detection and allowing the device to serve your needs:
lang and hreflang work well inside the data , but -- as far as I
have tested it -- they do not interact with the OS language, neither the
browser ( not to mention keyboards or peripherals)
I guess it was Adobe,
On 18.06.2015 12:01, Florian Rivoal wrote:
On 18 Jun 2015, at 10:58, cha...@yandex-team.ru wrote:
- jonnyr@
18.06.2015, 09:59, Jonny Rein Eriksen jon...@opera.com:
A possible solution:
If we had support for setting a standardized context attribute on the
input element, the browser could
On Thu, Jun 18, 2015 at 7:19 PM, Edward O'Connor eocon...@apple.com wrote:
On the other hand, link rel=mask-icon color=darkslategray seems like
it should Just Work™.
I guess we could add support for named colors to input type=color too.
--
https://annevankesteren.nl/
Hello All:Same solution than before. I knew there a library in the spec
of Adobe and its scripting languages ( a derivative of ECMA/DOM) that
implemented IME as well. Like a charm.
For virtual kybrds , specially.
As before, It would be nice that someone at Adobe Inc. could introduce
us to
Hi,
Kornel wrote:
Safari[…] uses `theme-color` for foreground color of favicons of
pinned tabs, but other browsers use `theme-color` for background
colors.
I replied:
Well, meta name=theme-color is not specced as speficially a
foreground or background color; it's a color that user agents
Hi Anne,
You wrote:
On the other hand, link rel=mask-icon color=darkslategray seems
like it should Just Work™.
I guess we could add support for named colors to input type=color
too.
Offhand I think that's a good idea. Probably won't round-trip through
typical color picker implementations,
On 6/18/15, Edward O'Connor eocon...@apple.com wrote:
Hi Anne,
You wrote:
On the other hand, link rel=mask-icon color=darkslategray seems
like it should Just Work™.
I guess we could add support for named colors to input type=color
too.
Offhand I think that's a good idea. Probably won't
On Thu, Jun 18, 2015, at 19:19, Edward O'Connor wrote:
Maciej replied:
I find this use case pretty compelling. There’s no reasonable set of
processing steps that could get you salmon pink for use as a
background, but black for use as a foreground. I think this is
compelling evidence that
On 18 Jun 2015, at 10:58, cha...@yandex-team.ru wrote:
- jonnyr@
18.06.2015, 09:59, Jonny Rein Eriksen jon...@opera.com:
A possible solution:
If we had support for setting a standardized context attribute on the
input element, the browser could keep a small database with configured
The problem:
When writing messages on Facebook, in web-mail, in discussion forums and
so on, we often end up switching languages for the spell-checker in the
desktop browser and on phones we switch which keyboard we use. Typically
I will write in English in messages to my English friends and
- jonnyr@
18.06.2015, 09:59, Jonny Rein Eriksen jon...@opera.com:
A possible solution:
If we had support for setting a standardized context attribute on the
input element, the browser could keep a small database with configured
settings per context.
There is an attribute called lang that
12 matches
Mail list logo
