- From: <Frederick.Hirsch@nokia.com>
- Date: Thu, 24 Jan 2013 19:15:29 +0000
- To: <anssi.kostiainen@nokia.com>
- CC: <Frederick.Hirsch@nokia.com>, <jackalmage@gmail.com>, <public-device-apis@w3.org>
[speaking not as chair] My concern was not with regards to the specific bug. I still think it not very good to have editors drafts where the date changes when you view them so you have no idea when the editor actually made an update, and I also think it is bad practice to rely on javascript generation which may fail in various contexts when it is fairly straightforward to generate plain html. Thus I haven't changed my view on the best practice. If Dom is able to automate this in the DAP context that would be great. As an editor in another work group I have made generating HTML as part of my personal work flow and it has been no big deal. regards, Frederick Frederick Hirsch Nokia On Jan 24, 2013, at 8:47 AM, Anssi Kostiainen wrote: > Hi Frederick, > > On 18.1.2013, at 16.56, ext Frederick.Hirsch@nokia.com wrote: > >> [- webapps] >> >> Tab, >> >> Thanks for checking. Before we close this issue we should resolve the point you mention below. >> >> Sorry about the trouble reaching the document. I believe editors should maintain ReSpec source in Overview.src.html and generate html for Overview.html so that the html is readable by all without issues, as well as having the correct generation date. Slightly more work for the editors with more usability for all the readers. I will raise this editorial issue again (I wasn't heard the last time) > > Given I've now fixed the issue (by using the same protocol to load the script as the document), I think this is not a high priority issue anymore? > > -Anssi
Received on Thursday, 24 January 2013 19:16:02 UTC