ntence (e.g. just dropping sections
and a few odds and ends) then you can simply keep pulling the LS and
apply code that filters out what you don't want.
--
Robin Berjon - http://berjon.com/ - @robinberjon
primitives. But TC39 does not seem
particularly receptive unless it comes with a way for someone to
participate in the structured cloning algorithm with custom objects.
Does this have to be any more complicated than adding a toClone()
convention matching the ones we already have?
--
Robin Berjon - http
-parsing logic is set up so
that things work without special effort.
Or even go the extra mile and just slurp all SVG elements into the HTML
namespace. There are a few name clashes, but we ought to be able to iron
those out.
And ditto MathML.
--
Robin Berjon - http://berjon.com
;t on the WG.
Apart from that, it should be included in the SotD and in the big red box.
So?
--
Robin Berjon - http://berjon.com/ - @robinberjon
years behind what implementations actually need to
implement for interoperability).
I'm happy to ask to change the "Call for Implementations" to something
else, but that will require some time.
So. Do you think that can make for a good starting point?
--
Robin Berjon - http://berjon.com/ - @robinberjon
On 10/09/2014 18:48 , Marcos Caceres wrote:
This is a formal objection to publication of this specification.
The rationale for the objection was already sent to the wwwprocess list.
Would you lift yours if Domenic lifted his?
--
Robin Berjon - http://berjon.com/ - @robinberjon
of you to not feed this thread as it can't possibly
lead anywhere useful.
--
Robin Berjon - http://berjon.com/ - @robinberjon
ry about that as much
as needed, which shouldn't be a lot. We can work something out and come
back to you with a solution to make this happen.
--
Robin Berjon - http://berjon.com/ - @robinberjon
anything about contenteditable.
Oh yeah, anything involving tracking, OT, or whatever temporal really,
really can't use the markup as its model. I'm surprised ICE went that
way, it must be terribly painful.
--
Robin Berjon - http://berjon.com/ - @robinberjon
es an HTML editor as a frontend but a
different document model as a backend
I don't know if we want to mention MVC and other such things? Perhaps
just the general sanity of not using your rendering view as your model :)
--
Robin Berjon - http://berjon.com/ - @robinberjon
On 23/06/2014 18:25 , Julie Parent wrote:
Well stated. I like contentEditable=cursor.
Works for me. Should I just scare up a draft? It is likely to be a
pretty short spec :)
--
Robin Berjon - http://berjon.com/ - @robinberjon
ngs are exposed and others aren't.
>
Good point.
--
Robin Berjon - http://berjon.com/ - @robinberjon
o the
side of the page being selected. But with the logical document order you
use, it would get selected. Do you make use of selection-preventing tricks?
These likely have their own amusing interactions with deletion: if you
make the footnote non-selectable but wish to drop it when a selection
encompassing it is deleted, you're facing a fun new challenge.
--
Robin Berjon - http://berjon.com/ - @robinberjon
7;s cleaner — the idea
is the same (and I certainly won't argue bikeshedding :).
--
Robin Berjon - http://berjon.com/ - @robinberjon
nk that the (limited) benefits are really worth it.
--
Robin Berjon - http://berjon.com/ - @robinberjon
else by default. Native UI atop custom editing is really a
solution for breakage.
We can also make it smart and able to tap into higher-level intention
events such as knowing the platform's localised shortcut for a given action.
--
Robin Berjon - http://berjon.com/ - @robinberjon
CC
me.
Maybe you'll be interested in signing up to the new public-editing-tf
list which has much lower traffic.
--
Robin Berjon - http://berjon.com/ - @robinberjon
On 06/06/2014 19:13 , Ryosuke Niwa wrote:
On Jun 6, 2014, at 7:24 AM, Robin Berjon wrote:
In order to handle them you have two basic options:
a) Let the browser handle them for you (possibly calling up some
platform functionality). This works as closely to user expectations
as a Web app can
On 06/06/2014 18:52 , Ryosuke Niwa wrote:
On Jun 6, 2014, at 6:40 AM, Robin Berjon wrote:
On 05/06/2014 09:02 , Ryosuke Niwa wrote:
I agree visual selection of bidirectional text is a problem
worth solving but I don't think adding a generic multi-range
selection support to the degree
s) people cross-post. After that, though, all discussion ought to
have been redirected there.
Thanks!
[0] http://lists.w3.org/Archives/Public/public-webapps/2014AprJun/0842.html
[1] http://w3c.github.io/editing-explainer/tf-charter.html
--
Robin Berjon - http://berjon.com/ - @robinberjon
f new
gTLDs has on software implementation.
The continued growth of https://publicsuffix.org/ would be annoying.
Can you think of an alternative? Because it's looking like we're going
to keep getting a lot of new TLDs.
--
Robin Berjon - http://berjon.com/ - @robinberjon
re trying to appeal to a specific audience
+1
+1
ACTION: Robin to create an Editing TF [recorded in
[13]http://www.w3.org/2014/06/06-webapps-minutes.html#action01]
Created ACTION-731 - Create an editing tf [on Robin
Berjon - due 2014-06-13].
BenjamP: we need a normative sp
bridge then, but the v1 of this project should IMHO really, really not
do more than what's needed for a script to cleanly implement an
arbitrary text editor.
--
Robin Berjon - http://berjon.com/ - @robinberjon
On 05/06/2014 09:09 , Ryosuke Niwa wrote:
On May 23, 2014, at 1:37 PM, Robin Berjon wrote:
Semantically, autocorrect and compositing really are the same
thing.
They are not. Word substations and input method compositions are
semantically different operations.
Ok, I'll accept
niceties). It's not the end
of the world, but it's a bit of extra complexity. Reusing the attribute
name and giving it a value that triggers new behaviour doesn't bring in
the complications, but it does give us a relatively clean syntax entry
point.
--
Robin Berjon - http://berjon.com/ - @robinberjon
DOM API perhaps as you're not going to get far without
scripting anyway?
I prefer it to be possible to say [contentEditable] { outline: dotted
1px; }. There's :read-write but it also matches input/textarea.
--
Robin Berjon - http://berjon.com/ - @robinberjon
On 02/06/2014 23:01 , Ben Peters wrote:
From: Robin Berjon [mailto:ro...@w3.org] I think that the latter is
better because it gives the library the computed range that matches
the operation, which as far as I can imagine is what you actually
want to check (e.g. check that the newRange does not
pplying editing operations to a multi-range selection is
a nightmare.
I don't disagree that it can be hard to handle, but I'm not sure that
that's indicative of anything. Most scripts only handle one selection
because AFAIK only Gecko ever supported more than one.
--
Ro
ld IMHO be painful.
Do you ever need a select-all event? I would think that a selection
change event that happens to give you a selection object containing
everything might suffice? (Which sort of seems to be what you're saying
here — hence checking where you stand.)
--
Robin Berjon - ht
all know is a terrible mess. If you don't
have reliable default behaviour, can you really rely on the browser to
DTRT for the cases you don't wish to handle? Won't you end up having to
use a library anyway?
Again, I'm all for the simplicity; I'm just worried about the snoring
dragon.
--
Robin Berjon - http://berjon.com/ - @robinberjon
not
wide open.
So I would say there's a risk, but not a huge one. That said, I still
prefer Simon's approach.
PS: I've been wondering if adding an HTML sanitiser to the platform
might make sense.
--
Robin Berjon - http://berjon.com/ - @robinberjon
eatures. Another approach is to add a
"submittable" attribute that can make the innerHTML of any element
contribute to the form data set.
Thoughts?
--
Robin Berjon - http://berjon.com/ - @robinberjon
On 27/05/2014 01:52 , Ben Peters wrote:
From: Robin Berjon [mailto:ro...@w3.org] On 23/05/2014 01:23 , Ben
Peters wrote:
As I said I am unsure that the way in which composition events
are described in DOM 3 Events is perfect, but that's only
because I haven't used them in anger and t
.)
Is that the sort of flow you had in mind?
PS: note I just noticed that the code in the Gist was not the latest I
had and had a lot of "TODO" bits — I've udpated it to the latest.
--
Robin Berjon - http://berjon.com/ - @robinberjon
se an unselectable attribute would make
sense. (I reckon that setting the widget to be cE=false would have the
same effect, but it is nevertheless an orthogonal property.)
WDYT?
--
Robin Berjon - http://berjon.com/ - @robinberjon
Hi Ben,
On 27/05/2014 02:07 , Ben Peters wrote:
From: Robin Berjon [mailto:ro...@w3.org] Even without accounting
for touch screens, you really want the platform to be the thing
that knows what Ctrl-Shift-Left means so you don't have to support
it yourself (and get it wrong often).
Agree
On 27/05/2014 01:47 , Ben Peters wrote:
-Original Message- From: Robin Berjon
On 26/05/2014 05:43 , Norbert Lindenberg wrote:
Were any speakers of bidirectional languages in the room when
this was discussed?
I don't know what languages the others speak. That said, my
recollectio
etc.
Range.prototype.style seems complex in the context of overlapping
ranges and such. Suddenly you're no longer applying CSS to a tree.
So, since Gecko supports that, do you know how it's done?
--
Robin Berjon - http://berjon.com/ - @robinberjon
On 26/05/2014 05:43 , Norbert Lindenberg wrote:
On May 23, 2014, at 5:19 , Robin Berjon wrote:
Which brings me to think: when we discussed this at the Summit,
there was some agreement (between all four of us :) that it was a
good idea to support multi-range selections. These are useful not
On 23/05/2014 21:32 , Jonas Sicking wrote:
On Fri, May 23, 2014 at 4:43 AM, Robin Berjon wrote:
On 23/05/2014 12:28 , Jonas Sicking wrote:
And on mobile autocorrect of misspelled words is common, though that
can probably be handled by moving the selection to the misspelled word
and then
On 23/05/2014 14:33 , James Greene wrote:
I'm all in favor of a new API as well.
Me too, as discussed in
http://lists.w3.org/Archives/Public/public-webapps/2014JanMar/0550.html.
I wouldn't put this on window though; why not put it on Selection?
--
Robin Berjon - http://
he same thing, which then makes editing that DOM more
complex. It would be awesome to find ways to enable styling ranges
which would allow them to keep a simpler DOM.
It would actually be pretty awesome.
--
Robin Berjon - http://berjon.com/ - @robinberjon
the case you're thinking of?
--
Robin Berjon - http://berjon.com/ - @robinberjon
forgotten stuff though (notably paste filtering, which
I'm unsure how to best handle here — see comments). Please review the
code so that we have an idea for a baseline of what we'd like to get at
the end.
--
Robin Berjon - http://berjon.com/ - @robinberjon
ype="insertText".
This would be the corollary to execComamnd("insertText"), and the
data would be the ñ that is about to be inserted.
But if you only get one event you can't render the composition as it is
carrying out.
--
Robin Berjon - http://berjon.com/ - @robinberjon
p with the a new mess
that just works differently.
But if we can make the code that a page needs to write in order to
handle the text mutation relatively simple, even when handling
composition, then I think we should leave it up to the page.
I think that we can make it reasonably easy to handle composition by
using composition events.
--
Robin Berjon - http://berjon.com/ - @robinberjon
not be visual), it
is only the way in which it is reported (in terms of the Selection API)
to the application that matters.
It makes for a pretty short spec — the previous paragraph is more than
enough ;)
--
Robin Berjon - http://berjon.com/ - @robinberjon
es, make tweaks that may be needed, etc.
See:
http://discourse.specifiction.org/
Feedback welcome!
--
Robin Berjon - http://berjon.com/ - @robinberjon
the world, but you need to think about it or you are guaranteed to mess
things up). This is probably acceptable at this level, libraries can
make it easier.
--
Robin Berjon - http://berjon.com/ - @robinberjon
27; code to get a feel for how much it
would actually help.
--
Robin Berjon - http://berjon.com/ - @robinberjon
ouldn't just add a copy() method to the
Selection object (or maybe Range), define it as doing whatever the
browser does when the copy operation is invoke with that given
selection, and ship.
--
Robin Berjon - http://berjon.com/ - @robinberjon
ile
API's issue to solve so +1.
--
Robin Berjon - http://berjon.com/ - @robinberjon
ipt loading is relatively common); but it's likely worth checking the
result.
--
Robin Berjon - http://berjon.com/ - @robinberjon
at's a whole other kettle of fish.
--
Robin Berjon - http://berjon.com/ - @robinberjon
false in both Firefox and Chrome.
See http://caniuse.com/#search=matches. You do get mozMatchesSelector
(and variants) in there.
--
Robin Berjon - http://berjon.com/ - @robinberjon
od joke and I reckon the thread of children jokes
in the parsing algorithm might fall in that category :)
I went with "template content parenting".
8.2.5.3 Foster Parenting
I think the foster parenting description is now complex enough that it
should be factored into an algor
s fitting
for the current feature, where as "templating" is more of a common
description for a development pattern.
I think that makes sense; I've made the change.
Feel free to tell me I'm nuts =-).
I reckon you are, but for different reasons altogether ;)
--
Robin Berjon - http://berjon.com/ - @robinberjon
ity (e.g. adding the identity to the
origin so that things like storage key off that and users sharing the
same device don't expose their data to one another).
--
Robin Berjon - http://berjon.com/ - @robinberjon
On 14/06/2013 19:26 , Ian Hickson wrote:
On Fri, 14 Jun 2013, Dirk Schulze wrote:
On Jun 14, 2013, at 6:41 AM, "Robin Berjon" wrote:
now that is in HTML, I was wondering if some of the other
specs needed the same treatment.
Some of the specs can be relevant for other specificatio
can be rather confusing to implement.
--
Robin Berjon - http://berjon.com/ - @robinberjon
onkey patching alone (a bit painful)? Just
import the monkey patching into HTML, remove it from that spec, and have
HTML refer to CE? Bring everything in?
Imports: This one monkey patches a lot. I reckon it's best to import
(ha!) it.
WDYT?
--
Robin Berjon - http://berjon.com/ - @robinberjon
tooth comb (using the diffs to
find where various parts ended up in the spec if needed) and check that
I didn't break anything.
Templates are a wicked cool brick, thanks!
--
Robin Berjon - http://berjon.com/ - @robinberjon
On 06/06/2013 15:08 , Johannes Wilm wrote:
This used to work some days ago:
https://dvcs.w3.org/hg/editing/raw-file/tip/editing.htm
You're missing an "l" at the end of your link...
--
Robin Berjon - http://berjon.com/ - @robinberjon
y something that I'd like to
see happen.
--
Robin Berjon - http://berjon.com/ - @robinberjon
id, but who cares about
validity :) It works.
b) the effects created by including the same link href multiple times in
the same doc
No effect whatsoever beyond wasted resources.
--
Robin Berjon - http://berjon.com/ - @robinberjon
en you have this:
The chances are good that the browser would issue several of those
requests before the first one returned with the information telling it
to look in the bundle. That means it would return the bundle several
times. Definitely a loss.
Or did I misunderstand what you h
On 10/05/2013 03:23 , Jonas Sicking wrote:
On Thu, May 9, 2013 at 9:36 AM, Marcos Caceres wrote:
On Wednesday, May 8, 2013 at 2:05 PM, Robin Berjon wrote:
How do you figure out media types? Is it just sniffing, or do you have
some sort of file extensions mapping as well?
Sniffing would
e to be supported by "everyone", because
past critical mass there would be too many "nobody noticed the fallback
is not working until now" cases, so that seems rather uninteresting in
the longer term.
It's valuable in order to get to the critical mass.
--
Robin Berjon - http://berjon.com/ - @robinberjon
ed.
How do you figure out media types? Is it just sniffing, or do you have
some sort of file extensions mapping as well?
--
Robin Berjon - http://berjon.com/ - @robinberjon
On 08/05/2013 01:39 , Glenn Maynard wrote:
On Tue, May 7, 2013 at 9:29 AM, Robin Berjon mailto:ro...@w3.org>> wrote:
Have you looked at just reusing JAR for this (given that you support
it in some form already)? I wonder how well it works. Off the top of
my head I see at lea
On 07/05/2013 22:31 , David Sheets wrote:
On Tue, May 7, 2013 at 3:29 PM, Robin Berjon wrote:
WDYT?
This is really cool!
Glad you like it :)
Most servers already contain support for this in the form of index files.
If you do
and set your server's file directory resolver to
one, no nested URL
scheme the way JAR does it (which is quite distasteful), no messing with
escaping ! in paths, etc.
WDYT?
--
Robin Berjon - http://berjon.com/ - @robinberjon
streamable. Without boiling the ocean, adding support for a streamable
format (which I don't think needs be more complex than tar) would be a
big plus.
* Captain Obvious to the rescue!
--
Robin Berjon - http://berjon.com/ - @robinberjon
than pushed off to a CG. It's not experimental in nature.
--
Robin Berjon - http://berjon.com/ - @robinberjon
ch (and it can make you aware of
corner cases or problems you hadn't thought of). Put differently, I
think it can be a lot less boring if you're getting something out of it.
--
Robin Berjon - http://berjon.com/ - @robinberjon
and such has found them to be
good. The point is to get some eyeballs that aren't the author's to look
at the tests before they go in; whatever process makes that happen is
good so long as it does not involve bureaucracy.
--
Robin Berjon - http://berjon.com/ - @robinberjon
e realise there's zero overhead for regular
contributions.
--
Robin Berjon - http://berjon.com/ - @robinberjon
On 04/04/2013 17:59 , Arthur Barstow wrote:
On 4/4/13 10:23 AM, ext Robin Berjon wrote:
after having moved the test suite to the GitHub repository, we've been
busy cleaning things up.
Can the mirroring to <http://w3c-test.org/web-platform-tests/master/> be
more frequent than every
very
satisfactory and appreciated,
Glad you like it :)
--
Robin Berjon - http://berjon.com/ - @robinberjon
traight for:
https://github.com/w3c/web-platform-tests/pulls
Let's party!
A big thanks to Ms2ger and Odin for helping a lot with cleaning up the
moved repo!
--
Robin Berjon - http://berjon.com/ - @robinberjon
On 04/04/2013 15:41 , Simon Pieters wrote:
On Wed, 03 Apr 2013 14:50:53 +0200, Robin Berjon wrote:
On 29/03/2013 21:08 , Jonas Sicking wrote:
* Cache both files (poor bandwidth)
* We could enable some way of flagging which context different URLs
are expected to be used in. That way the UA can
note that I've removed the widgets tests. It's a great test
suite, but widgets don't seem to be part of the web platform today, and
so they shouldn't be in there.
I'm going to sunset the hg repository by making it read only as soon as
I can remember how that work
f the form { "video/webm": "kittens.webm",
"video/evil": "dead-kittens.mv4" } that would operate in a manner
modelled on , caching only what's needed.
It's a bit verbose, but it's a lot less verbose than loading the content
twice.
--
Robin Berjon - http://berjon.com/ - @robinberjon
Hi Chaals,
On 24/03/2013 01:33 , Charles McCathie Nevile wrote:
2. Bundles.
Sometimes we need to load several resources (js/css/json/...) before we
can actually show something to user. Like a dialog, or another complex
control. Or if it's a single page application before change "page".
Again, it
On 18/03/2013 15:54 , Dimitri Glazkov wrote:
I am a big fan.
Yeah, I kinda like the idea as well.
--
Robin Berjon - http://berjon.com/ - @robinberjon
ope there already.
All of the above assumes you're all happy with it, and the HTML people
too. I reckon it could work though.
--
Robin Berjon - http://berjon.com/ - @robinberjon
t API
(11 passes and 2 fails).
Thanks!
Based on this and other feedback, I've applied the change. We're now
using webidl2.js by default.
--
Robin Berjon - http://berjon.com/ - @robinberjon
https but uses a stylesheet served
over http. This does not work in Chrome and will soon stop working in
Firefox (https://bugzilla.mozilla.org/show_bug.cgi?id=834836).
--
You are receiving this mail because:
You are the assignee for the bug.
--
Robin Berjon - http://berjon.com/ - @robinberjon
erms.html
That's one of the reasons we have a SysApps WG today. As it happens,
they're working on a security model, too.
This is not to say that declaring required privileges cannot be useful.
There certainly are cases in which it can integrate into a larger
system. But t
that worse.
--
Robin Berjon - http://berjon.com/ - @robinberjon
metadata
but with usability taken into account.
What is the expectation for what I will characterize as "legacy"
specs like Marcos' widget test suites? Marcos?
I would say: whoever wants to include their stuff can include it, so
long as it's legit content related to a spec.
--
Robin Berjon - http://berjon.com/ - @robinberjon
On 31/01/2013 01:27 , Glenn Adams wrote:
btw, it seems that Robin hasn't updated the generated copyright to
include Beihang
Which will happen before the end of the grace period.
--
Robin Berjon - http://berjon.com/ - @robinberjon
orted. (In
webidl2.js that is, not idlharness.js).
--
Robin Berjon - http://berjon.com/ - @robinberjon
one says anything) I'll merge the changes to the master branch.
Thanks!
--
Robin Berjon - http://berjon.com/ - @robinberjon
orthogonal to the GitHub reorg. You can keep using the existing
framework after the GitHub move, and it would still have the same
problems if we don't move.
--
Robin Berjon - http://berjon.com/ - @robinberjon
we can reassess. At this point I
should probably stop belabouring my point because I'm this close to
using the word "agile".
--
Robin Berjon - http://berjon.com/ - @robinberjon
On 22/01/2013 17:14 , Tobie Langel wrote:
On 1/22/13 4:45 PM, "Robin Berjon" wrote:
You *do* need to make the proper commitments for the test suite, but
those are much lighter and can easily be extended to all.
Moving to GitHub should be an excellent occasion to revisit how the CLA
ut they're
just listed as the individual specs. We can keep on adding more specs in
there (the Web Crypto people are looking to do that).
--
Robin Berjon - http://berjon.com/ - @robinberjon
tuff.
Anyway, for my part, the how-to-split repository issue is not that
important compared to having the tests at GitHub in the first place :-)
Agreed. But how about we start with just one repo and then split them
into several if it's a problem?
--
Robin Berjon - http://berjon.com/ - @robinberjon
gets used.
--
Robin Berjon - http://berjon.com/ - @robinberjon
1 - 100 of 577 matches
Mail list logo
