14067 2011-09-07 19:36:47 +0000 Value for createLink and unlink can be null instead of a string 2011-09-15 22:28:02 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - HTML Editing APIs unspecified All All RESOLVED FIXED P2 normal --- 1 ayg ayg mike public-webapps sideshowbarker+html-editing-api oldest_to_newest 56484 0 ayg 2011-09-07 19:36:47 +0000 Values should all be strings. No browser returns values at all for these; I should just remove value/indeterm for now from createLink/unlink. 56864 1 ayg 2011-09-15 21:10:33 +0000 https://dvcs.w3.org/hg/editing/rev/d0760b6d50a5 56867 2 ayg 2011-09-15 21:27:48 +0000 The change was broken, reverted: https://dvcs.w3.org/hg/editing/rev/2d9559086d05 Won't reinstate until I have the tests regenerated. 56869 3 ayg 2011-09-15 21:50:19 +0000 Turns out there are multiple places where we call queryCommandValue() for createLink, or refer to its value. As far as I can tell, the only cases right now are in "record current states and values" and "restore states and values". Working around these is not entirely trivial, since we have to support value overrides in the latter case. I'll have to add special cases for createLink. Already done for the former, now need to do it for the latter. Obnoxiously, it takes ten minutes or so to generate the tests and spot these bugs . . . 56870 4 ayg 2011-09-15 22:28:02 +0000 Fixed properly this time: https://dvcs.w3.org/hg/editing/rev/3cc579b879ac Where "properly" means "with more special cases", naturally. But it works.