, that would be a
consistent and learnable way for users to limit their searches.
Dave
--
David Young
dyo...@pobox.comUrbana, IL(217) 721-9981
, now, would be tractable with the
right HTML/CSS primitives. If you have something like this underway,
please get in touch.
Dave
--
David Young
dyo...@pobox.comUrbana, IL(217) 721-9981
on, definitely shouldn't get a prime share unless the user has made
an explicit grant. Give the bulk of the resources to what you could
conceivably be looking at.
Do you see what I'm getting at?
Dave
--
David Young
dyo...@pobox.comUrbana, IL(217) 721-9981
On Fri, May 09, 2014 at 11:05:03AM -0500, Glenn Maynard wrote:
On Fri, May 9, 2014 at 9:56 AM, David Young dyo...@pobox.com wrote:
The algorithms don't have to run as fast as possible, they only have to
run fast enough that the system is responsive to the user. If there is
a motion
for.
Is there some reason that the web platform does not support this
approach? Is there some reason that this approach doesn't fit the use
cases you mention?
Dave
--
David Young
dyo...@pobox.comUrbana, IL(217) 721-9981
On Mon, May 05, 2014 at 01:05:35PM -0700, Rik Cabanier wrote:
On Mon, May 5, 2014 at 11:10 AM, David Young dyo...@pobox.com wrote:
On Sat, May 03, 2014 at 10:49:00AM -0700, Adam Barth wrote:
Over on blink-dev, we've been discussing [1] adding a property to
navigator
that reports
a microphone from
an app? How do I know which microphones are connected to which apps?
Ian's proposal seems to offer this visibility and control to the user.
Dave
--
David Young
dyo...@pobox.comUrbana, IL(217) 721-9981
think that if I was going to make engineering suggestions, they would
be for the browser makers, not for you, Ashley.
Dave
--
David Young
dyo...@pobox.comUrbana, IL(217) 721-9981
by application JavaScript.
Dave
--
David Young
dyo...@pobox.comUrbana, IL(217) 721-9981
On Fri, Jan 04, 2013 at 03:34:11PM -0800, Tab Atkins Jr. wrote:
On Sat, Dec 29, 2012 at 10:17 AM, David Young dyo...@pobox.com wrote:
On Sat, Dec 29, 2012 at 01:23:20AM +, Ian Hickson wrote:
On Sun, 23 Oct 2011, Eric Sh. wrote:
I was trying out the HTML5 context menu in firefox
menu (click), and a second
gesture for the app context menu (shift-click), OR
2) always add the UA items to the context menu in consistent places, for
example by adding app-specific context menu items after UA items
Dave
--
David Young
dyo...@pobox.comUrbana, IL(217) 721-9981
. Mainly I am interested in
collaborating with others to develop new web-editing practices. If you
can refer me to a more suitable list for that sort of discussion, I
would owe you a debt of gratitude.
Now, back to lurking mode. :-)
Dave
--
David Young
dyo...@pobox.comUrbana, IL(217) 721
On Mon, Apr 30, 2012 at 08:55:04AM +0300, Aryeh Gregor wrote:
On Sun, Apr 29, 2012 at 11:39 PM, David Young dyo...@pobox.com wrote:
I'm curious what advantages document.execCommand() has over the
customary DOM API for adding/deleting/moving nodes?
execCommand() does vastly more complicated
it is necessary to insert two spaces before a br
appears; the br cannot be deleted, not even by inserting a space. :-)
Dave
--
David Young
dyo...@pobox.comUrbana, IL(217) 721-9981
are there in each of those strings? I think
that if there is more than one possible cursor position, then the state
of the editor is some content instead of no content.
I submit that only the empty string (value == '') is no content. :-)
Dave
--
David Young
dyo...@pobox.comUrbana, IL(217) 721
and indicates its presence. You could use a
return symbol, ⏎, or interpunct, ·, for the purpose. In the example
pfont color=redbr/font/p, color that character red.
Dave
--
David Young
dyo...@pobox.comUrbana, IL(217) 721-9981
On Sun, Apr 29, 2012 at 11:30:20PM -0400, Boris Zbarsky wrote:
On 4/29/12 11:24 PM, David Young wrote:
It seems that the text contents of atextarea, at least, could be
properly in the DOM?
Not really: when you type in a textarea, that doesn't change its
actual DOM kids. Both per spec
On Mon, Apr 30, 2012 at 08:55:04AM +0300, Aryeh Gregor wrote:
On Sun, Apr 29, 2012 at 11:39 PM, David Young dyo...@pobox.com wrote:
I'm curious what advantages document.execCommand() has over the
customary DOM API for adding/deleting/moving nodes?
execCommand() does vastly more complicated
() has over the
customary DOM API for adding/deleting/moving nodes?
Dave
--
David Young
dyo...@pobox.comUrbana, IL(217) 721-9981
means in this context), is that for some reason, or is it
just a historical artifact?
Dave
--
David Young
dyo...@pobox.comUrbana, IL(217) 721-9981
attribute
instead of a subordinate text node, so I suppose DOM Range may be less
sensible and/or more difficult to apply there.
If Ryosuke wants to use one API to address ranges of text be they part
of a text control or not, then that makes sense to me.
Dave
--
David Young
dyo...@pobox.com
21 matches
Mail list logo
