I still believe that basing anything on keycode, although an obvious
thing to do, will leave lead to unnecessary fragility in the users of
this API. I understand that we ultimately will be generating
WebInputEvents, but the level of abstraction used by the API should be
a level higher than as
The easiest thing for someone who's attempting to use the
accessibility API may be to avoid using keycodes, and instead allow
the input of the desired displayed value. The advantage of this would
be to allow the input of internationalized characters that would
otherwise need IME to be input.
On Thu, Jan 14, 2010 at 4:15 PM, Dominic Mazzoni dmazz...@google.com wrote:
On Thu, Jan 14, 2010 at 8:01 AM, Simon Stewart
simon.m.stew...@gmail.com wrote:
The easiest thing for someone who's attempting to use the
accessibility API may be to avoid using keycodes, and instead allow
the input
?
- a
On Fri, Nov 27, 2009 at 10:43 AM, Simon Stewart
simon.m.stew...@gmail.com wrote:
Hi,
How do I track the containment relationship of the ports associated
with frames from within an extension? That probably makes no sense, so
an example might help :)
Chrome loads a page (http://example.com
My main problem with that is that it's a horrible end-user experience
--- All I want is this extension, and I don't know which of these
plethora of choices to pick. My preference, both as a user and a
developer of extensions, would be to make it easy to package
everything up so as to provide a
This feels a little off topic (from chrome dev), so please feel free
to follow up off-list.
One way is to use the latest version of webdriver, built from the its
subversion repo:
http://selenium.googlecode.com/
I'm not quite sure what you're trying to do with the automated Chrome
though, so
What about different bitness? Most OS versions come in 32 and 64 bit
flavours, and this specification doesn't seem to allow this
differentiation.
Simon
On Fri, Sep 4, 2009 at 1:51 AM, Matt Perry mpcompl...@chromium.org wrote:
Right now we have this manifest key for plugins: plugins: [
{path:
We recently landed support for using Chrome into WebDriver, and will
shortly be making a set of downloads available. This would allow you
to remote control an instance of Chrome using something like:
WebDriver driver = new ChromeDriver();
driver.get(http://www.example.com;);
The code is hosted
I thought that the AutomationProxy wasn't available in released
versions of Chrome A look at the symbols exported by the
chrome.dll suggests that this is the case.
Simon
On Thu, Sep 3, 2009 at 11:07 PM, Paweł Hajdan Jr.
phajdan...@chromium.org wrote:
Then probably you should just use
This is something along the lines of calling IWebBrowser2.get_HWND or
(more similarly) using XPCOM's nsIAccessibleDocument-GetWindowHandle
() calls:
http://msdn.microsoft.com/en-us/library/aa454384.aspx
https://developer.mozilla.org/En/NsIAccessibleDocument/windowHandle
Both of these provide a
10 matches
Mail list logo
