Re: [whatwg] Fixing undo on the Web - UndoManager and Transaction
Hi all, I've uploaded my proposal: http://rniwa.com/editing/undomanager.html Summary of changes: - *Section 3.2 Automatic transactions* is rewritten - Removed *A proper sequence of automatic transactions* - Added *3.2.1. Undoability and Redoability of Automatic Transactions*to clarify when an automatic transaction can be unapplied and reapplied safely - isReapply argument is added to apply method of Transaction interface - isAutomatic attribute is added to Transaction interface - Partial interfaces are added for Document and Element interfaces to define undoManager and undoScope IDL attributes - label attribute of Transaction interface can return null now, and the spec allows UAs to use a part of the value as supposed to the whole (e.g. when it's too long) - Ryosuke
[whatwg] Geographic hyperlinks
http://forums.whatwg.org/bb3/viewtopic.php?f=3t=4725 [Topic has been on forum for 2 weeks without reply. Now posting to mailing list.] -- Hyperlinks for geographic coordinates are a mess. Designers of web applications are being forced to design their own solutions to make geographic links more user-friendly... http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Geographical_coordinates http://toolserver.org/~geohack/geohack.php?pagename=Londonparams=51_30_26_N_0_7_39_W_type:city(7825200)_region:GB There's a relatively simple solution to all of this that could easily be upgraded over time. We already have mailto:; hyperlinks, for example, that accept certain fields and map those to certain parameters within a user-definable (or system-specific) mail client application. The same could be done for geographic data. The user might install certain geographic information systems on their viewing device, specify their favourite for geo: links, and then when they follow a hyperlink with geographic content, any relevant information fields present might be transferred over to the geographic information system (GIS) as coordinates. I suggest for the HTML standards people to simply talk to Wikipedia or Google and copy their system, as a starting-point for discussion at least. Maybe their format could be tidied up slightly, but generally I think they've done a good job and that their work should be adopted as a standard, so that you don't end up seeing pages with dozens of hyperlinks (one for each GIS) as we do on Wikipedia. -- Matthew Slyman, M.A. Computer Science (Camb)
Re: [whatwg] Geographic hyperlinks
See RFC 5870[1] for a proposed standard geo URI scheme for geo: hyperlinks. - Tantek [1] http://tools.ietf.org/html/rfc5870 On Mon, Oct 10, 2011 at 10:27, Matthew Slyman wha...@aaabit.com wrote: http://forums.whatwg.org/bb3/viewtopic.php?f=3t=4725 [Topic has been on forum for 2 weeks without reply. Now posting to mailing list.] -- Hyperlinks for geographic coordinates are a mess. Designers of web applications are being forced to design their own solutions to make geographic links more user-friendly... http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Geographical_coordinates http://toolserver.org/~geohack/geohack.php?pagename=Londonparams=51_30_26_N_0_7_39_W_type:city(7825200)_region:GB There's a relatively simple solution to all of this that could easily be upgraded over time. We already have mailto:; hyperlinks, for example, that accept certain fields and map those to certain parameters within a user-definable (or system-specific) mail client application. The same could be done for geographic data. The user might install certain geographic information systems on their viewing device, specify their favourite for geo: links, and then when they follow a hyperlink with geographic content, any relevant information fields present might be transferred over to the geographic information system (GIS) as coordinates. I suggest for the HTML standards people to simply talk to Wikipedia or Google and copy their system, as a starting-point for discussion at least. Maybe their format could be tidied up slightly, but generally I think they've done a good job and that their work should be adopted as a standard, so that you don't end up seeing pages with dozens of hyperlinks (one for each GIS) as we do on Wikipedia. -- Matthew Slyman, M.A. Computer Science (Camb) -- http://tantek.com/ - I made an HTML5 tutorial! http://tantek.com/html5
Re: [whatwg] Geographic hyperlinks
Bjoern Hoehrmann: * Christoph Päper wrote: geo:13.4125,103.8667@mars You can specify the coordinate reference system with the crs paramameter Yes, but I don’t think it’s a good design to select the astronomic body with the same property that you use to switch between different CRSs for a given spheroid. Nevermind.
Re: [whatwg] Geographic hyperlinks
You can define the crs (srsName) for a geo: link which effectively allows you to do that. See the registry in the spec. roBman On Mon, 2011-10-10 at 21:26 +0200, Christoph Päper wrote: Tantek Çelik: See RFC 5870[1] for a proposed standard geo URI scheme for geo: hyperlinks. I wonder whether this scheme, someday, will be extended to include a domain part, e.g. geo:13.4125,103.8667@mars, or whether we’ll rather get a ‘astro:’ scheme.
[whatwg] Undoscopes inside an editable region should ignored
Hi, Allowing authors to define an undoscope inside an editing host appears to be troublesome because user editing actions can modify the subtree of the host in very complex ways, and it's hard to understand which node may be mutated as a result of some editing actions or execCommand. Given that, I propose to ignore undoscope content attributes or assignments to undoScope IDL attribute if the content attribute is added to or the IDL attribute is set to true for an editable element. Furthermore, I propose to continue to ignore undoscope content attribute and keep undoScope IDL attribute false when the element becomes non-editable in the future (e.g. by removing contenteditable content attribute of its ancestor). Such a quirk is needed to avoid creating and destroying undoManager as a result of style recalculation in Mozilla and WebKit because both engines support -webkit-user-modify and -moz-user-modify to toggle editability. Best, Ryosuke Niwa Software Engineer Google Inc.
