On Sep 3, 2010, at 12:13 PM, Adam Barth wrote:
Sorry for not reading the document in detail, but are these events
fired synchronously or asynchronously?
Since it's all client-side communication between the web app and local user
agent, I don't have a preference. Chris may. Do you?
On Sep 3, 2010, at 5:25 AM, Mike Marchywka wrote:
Certainly an ability to zoom text is well known, but a text to
speech facility or re-rendering from web author's original
intent ( text to audio conversion) could be of general interest.
[ I guess this also motivates another general rant I
/dnd.html#undomanager
James Craig responded:
The main difference seems to be that our Undo and Redo *request* allows the
web application to determine what (if anything) should be undone, or redone,
where the HTML5 undo manager requires that the user agent make the change
directly to the DOM
On Nov 2, 2010, at 12:48 PM, Ojan Vafai wrote:
On Oct 27, 2010, at 2:57 PM, James Craig wrote:
James Craig responded:
The main difference seems to be that our Undo and Redo *request* allows
the web application to determine what (if anything) should be undone, or
redone, where the HTML5
On Nov 10, 2010, at 3:40 PM, Ojan Vafai wrote:
Heh. There's clearly still a good deal of confusion about what the intended
behavior here is. Well, I'm confused anyways. :)
On Fri, Nov 5, 2010 at 9:32 PM, James Craig jcr...@apple.com wrote:
Ojan Vafai wrote:
How
On Nov 26, 2012, at 2:01 PM, Steve Faulkner faulkner.st...@gmail.com wrote:
I have submitted a patch [1] to add main element support to webkit and
would appreciate your consideration.
You should also add a layout test.
From an accessibility perspective, the main element is an easy win.
On Nov 27, 2012, at 4:22 PM, Ian Hickson i...@hixie.ch wrote:
ARIA is used by very few authors, and those authors are, by and large,
much more competent than average. ARIA therefore tends to be used to a
much higher level of quality than most elements.
Yet this is part of the problem. One
Snipping somewhat for brevity…
On Nov 27, 2012, at 8:02 PM, Ian Hickson i...@hixie.ch wrote:
Sites have been quite happily working with a skip past navigation
link
Happily? Begrudgingly? For what it's worth, landmark navigation should not be
confused with skip nav links. Think of it more
On Nov 28, 2012, at 12:43 AM, Maciej Stachowiak m...@apple.com wrote:
role=main can achieve this, but sectioning elements take care of the other
landmark roles, and it seems strange to have this be the odd one out. In my
own judgment, this outweighs risk of misuse.
I agree.
On the other
On Nov 29, 2012, at 6:19 PM, James Robinson jam...@google.com wrote:
This is an interesting standards debate but as many people have noted it does
not belong on the webkit-dev list, which is for coordinating the development
of WebKit. Please take this over to whatwg@ or some other
On Nov 29, 2012, at 6:33 PM, James Craig jcr...@apple.com wrote:
On Nov 29, 2012, at 6:19 PM, James Robinson jam...@google.com wrote:
This is an interesting standards debate but as many people have noted it
does not belong on the webkit-dev list, which is for coordinating the
development
On Nov 29, 2012, at 7:10 PM, Ryosuke Niwa rn...@webkit.org wrote:
I don't see a harm in waiting another couple of weeks or months until
standards discussion settles assuming that the main element doesn't become
the longdesc of the next decade.
Don't confuse the two. The argument over the
On Nov 29, 2012, at 7:19 PM, Alex Russell slightly...@google.com wrote:
My object is somewhat different. I think it's useful for the readability
use-case (and the other proposed solutions are mostly bad jokes), but it
doesn't strike me that this give you much default UI and doesn't plumb
IMO, the following represents enough evidence to land the patch as soon as the
last layout test failure is resolved.
https://bugs.webkit.org/show_bug.cgi?id=103172
1. Sam Ruby, as Chair declared this passing the HTML WG vote, With no
objections and ample support, this resolution passes.
I wanted to give the list a heads up because the related issue was somewhat
controversial last time.
To give some context, this is about whether image alt text should be included
in the plain text pasteboard. Most everyone is of the opinion that it should,
but several of us feel that it
I'd like to see support for @inert subtrees prioritized if dialog is going to
be postponed. So many web authors are faking this behavior now, which is
problematic for full keyboard access and accessibility.
On Aug 29, 2013, at 10:50 AM, Ryosuke Niwa rn...@webkit.org wrote:
While I'd like to
On Aug 29, 2013, at 12:56 PM, Darin Adler da...@apple.com wrote:
On Aug 29, 2013, at 12:44 PM, James Craig jcr...@apple.com wrote:
I'd like to see support for @inert subtrees prioritized if dialog is going
to be postponed.
I don’t think dialog is being postponed; just that no one has
AX: Implement CSS -webkit-alt property
https://bugs.webkit.org/show_bug.cgi?id=120188
This is blocking 20+ bugs on one of our higher profile content sites and we’d
like to start work on it. To clarify, the problem is that with CSS generated
content in pseudo-elements like this:
, at 10:08 PM, James Craig jcr...@apple.com wrote:
AX: Implement CSS -webkit-alt property
https://bugs.webkit.org/show_bug.cgi?id=120188
This is blocking 20+ bugs on one of our higher profile content sites and we’d
like to start work on it. To clarify, the problem is that with CSS generated
On Oct 8, 2013, at 1:02 AM, Dirk Schulze dschu...@adobe.com wrote:
I hope you understand that I am not particularly concerned about Apples
screen reader solution. It is one implementation. I would like to know if
JAWS, NVDA, Dolphin and other are aboard.
Withe the exception of NVDA, the
I sometimes forget to run the check-webkit-style script before uploading
patches, so I put a patch up for review that adds a --style and --no-style
flags to prepare-Changelog and svn-create-patch. Alexey suggested I make it the
default, which I've done for prepare-Changelog, but not in
Yes, but not everyone uses the webkit-patch script in their workflow.
On Apr 4, 2014, at 7:27 AM, Brendan Long s...@brendanlong.com wrote:
Doesn't 'webkit-patch upload' already do that?
On 04/04/2014 02:14 AM, James Craig wrote:
I sometimes forget to run the check-webkit-style script
the change log creation, you'd never
be able to run prepare-Changelog without the --bug parameter, unless you
specifically disabled the style check with --no-style.
svn-create-patch:
- Add it! It's a good idea.
Cheers,
Zoltan
On Fri, Apr 4, 2014 at 7:41 AM, James Craig jcr
On Apr 4, 2014, at 1:33 PM, Zoltan Horvath zol...@webkit.org wrote:
On Fri, Apr 4, 2014 at 12:43 PM, James Craig jcr...@apple.com wrote:
On Apr 4, 2014, at 9:08 AM, Zoltan Horvath zol...@webkit.org wrote:
Hi there,
prepare-Changelog:
- The style checker script runs on the ChangeLogs
Thanks to Brendan, Alexey, Zoltan, and Daniel for the feedback on this, which
I've addressed. Any more comments? Thanks.
r?
On Apr 4, 2014, at 12:14 AM, James Craig jcr...@apple.com wrote:
I sometimes forget to run the check-webkit-style script before uploading
patches, so I put a patch up
Check out dumpAccessibilityChildren() in:
./LayoutTests/accessibility/aria-hidden-false-works-in-subtrees.html
Also look in:
./Tools/WebKitTestRunner/InjectedBundle/Bindings/AccessibilityUIElement.idl
./Tools/WebKitTestRunner/InjectedBundle/Bindings/AccessibilityController.idl
On Apr 23, 2014,
?
Thanks,
James Craig
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev
?
Thanks,
James Craig
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev
28 matches
Mail list logo
