Keeping it off by default until it has some mainstream acceptance
seems like a bit of a self-defeating policy for new features; is this
often done in WebKit?
-- Dirk
On Mon, Oct 4, 2010 at 10:12 PM, Maciej Stachowiak m...@apple.com wrote:
Since a ping has been controversial in the past (for
I don't think it is the norm. This one is special for the reasons already
stated.
-Darin
On Mon, Oct 4, 2010 at 11:17 PM, Dirk Pranke dpra...@chromium.org wrote:
Keeping it off by default until it has some mainstream acceptance
seems like a bit of a self-defeating policy for new features; is
On Mon, Oct 4, 2010 at 6:24 PM, Simon Fraser simon.fra...@apple.com wrote:
On Oct 4, 2010, at 5:30 PM, Simon Fraser wrote:
On Oct 4, 2010, at 2:33 PM, Adam Barth wrote:
As you might have noticed, the WebSocket tests are crashing on Leopard
and Snow Leopard. I thought for a while that this
-- Forwarded message --
From: Ryosuke Niwa ryosuke.n...@gmail.com
Date: Tue, Oct 5, 2010 at 2:29 AM
Subject: Re: [webkit-dev] Supporting css ime-mode property
To: Alexey Proskuryakov a...@webkit.org
Cc: Kenichi Ishibashi ba...@google.com, webkit-dev@lists.webkit.org
+1 for
05.10.2010, в 02:29, Ryosuke Niwa написал(а):
I highly doubt that people will misuse ime-mode because whether or not IME
should be active is usually obvious from the context (e.g. username
password, telephone number, etc...).
1. I sometimes use Cyrillic characters in user names, and I'm
On Tue, Oct 5, 2010 at 9:27 AM, Alexey Proskuryakov a...@webkit.org wrote:
So far, the only accurate use case that I've seen was developing a UI for a
back-end that doesn't support non-ASCII characters in some fields. I don't
think we should extend the Web platform just to support apps that
On 05.10.2010, at 10:12, Tony Chang wrote:
You could argue that the web site is broken because it should be able to
normalize this on the server, but that doesn't change the fact that there are
lots of web sites in Japan that already try to do this. Implementing
ime-mode would improve
-- Forwarded message --
From: Ryosuke Niwa ryosuke.n...@gmail.com
Date: Tue, Oct 5, 2010 at 10:45 AM
Subject: Re: [webkit-dev] Supporting css ime-mode property
To: Alexey Proskuryakov a...@webkit.org
Cc: Kenichi Ishibashi ba...@google.com, webkit-dev@lists.webkit.org
On Tue, Oct
On Tue, Oct 5, 2010 at 10:38 AM, Alexey Proskuryakov a...@webkit.org wrote:
There are big questions remaining:
- Do we really want to implement an IE extension in a way that's way
different from IE?
We support many features that IE initially implemented; HTML editing is a
good example.
On 05.10.2010, at 10:56, Ryosuke Niwa wrote:
- Do we really want to implement an IE extension in a way that's way
different from IE?
We support many features that IE initially implemented; HTML editing is a
good example.
How is this relevant? This topic is complicated as is, let's not
On Tue, Oct 5, 2010 at 11:26 AM, Alexey Proskuryakov a...@webkit.org wrote:
Also, I don't think the difference between IE and Firefox's
implementation affects CJK websites, which presumably will be the primary
users of ime-mode.
I think it does. An example that was given by Kenichi
On 05.10.2010, at 14:31, Ryosuke Niwa wrote:
That's exactly why we need to activate IME there. If I understood his
comment, Kenichi is saying that we need to activate IME to type names in
Katakana while we need to deactivate IME to type in card numbers, etc... not
that website disables
On Tue, Oct 5, 2010 at 3:04 PM, Alexey Proskuryakov a...@webkit.org wrote:
As far as I checked on Firefox 4.0b6, it is implemented and works as
expected. Do you have a different version of Firefox?
I tested https://www.aeoncredit.co.jp/NetBranch/cardinit.do with 3.6.10
on Mac.
It works
Though this property is useful in some situation, it's very confusing
regarding to its real purpose. If I understand correctly, this property is
mostly used for restricting the input character set of an input box. But an
IME is actually only one of many ways can be used by the user to input
On Tue, Oct 5, 2010 at 3:18 PM, James Su james...@gmail.com wrote:
Though this property is useful in some situation, it's very confusing
regarding to its real purpose. If I understand correctly, this property is
mostly used for restricting the input character set of an input box.
Not quite.
Hi Gustavo,
I think Webkit/EFL is now EFL backend independent isn't it?
I'm trying to build it over EFL/directfb librairies.
after calling the build-webkit --efl the build starts but after a while I
got the following error:
I set SET(CMAKE_VERBOSE_MAKEFILE ON) to get the full verbose.
2010/10/5 Ryosuke Niwa rn...@webkit.org
On Tue, Oct 5, 2010 at 3:18 PM, James Su james...@gmail.com wrote:
Though this property is useful in some situation, it's very confusing
regarding to its real purpose. If I understand correctly, this property is
mostly used for restricting the input
Hi,
Thanks a lot of discussion about this matter. A bunch of Ryosuke-san's
replies is exactly what I'd like to say. I still believe that the
property can make web page authors provide appropriate input mode by
default and isn't harmful as long as the authors use the property in a
gentle manner.
On Sep 24, 2010, at 8:02 PM, David Hyatt wrote:
This is a tough problem. It seems like you have to get involved in the line
layout code e.g., findNextLineBreak in order to really do the right thing.
findNextLineBreak uses an iterator that walks the objects, so it's easier to
tell what
I also have a concern on this proposal. The assumption that this property makes
on the semantic of the input system of the platform does necessary universally
true and it could be potentially harmful. On Mac OS X and iOS, there is no
notion of disabling or enabling input method or mode. You can
On 05.10.2010, at 17:16, Kenichi Ishibashi wrote:
Here is another use-case. Some modern CJK web pages provide a way to
input Chinese or Japanese text without OS-provided IMEs. You can see
an example at http://www.baidu.com/. Click the text next to the search
button and select 拼音 or
I meant does NOT necessary universally true. The property assumes input mode
takes two states, on and off, but on some platforms it can take multiple values.
an alternative way of achieving the same thing in more predictive way:
On Tue, Oct 5, 2010 at 5:48 PM, Alexey Proskuryakov a...@webkit.org wrote:
What I see on baidu.com right now seems much different from an input
method though - they are just making a guess at what the user intended to
type. Google search works exactly the same, as long as the page language is
On Oct 5, 2010, at 7:33 PM, Eric Mader wrote:
On Sep 24, 2010, at 8:02 PM, David Hyatt wrote:
This is a tough problem. It seems like you have to get involved in the line
layout code e.g., findNextLineBreak in order to really do the right thing.
findNextLineBreak uses an iterator that
05.10.2010, в 18:14, Ryosuke Niwa написал(а):
Select 拼音 and then try typing nihao into the search box. You get IME. It
even supports moving back forth between Chinese English mode by Shift key!
Per an off-list discussion, one needs to click 输入法 or the arrow next to it
and then you can
05.10.2010, в 21:42, Alexey Proskuryakov написал(а):
This page disables non-ASCII input sources in Firefox, and I wouldn't call it
a good idea
In other words, I think that it works better in Safari thanks to the lack of
ime-mode. I might be overlooking some missing functionality, but the
26 matches
Mail list logo
