- From: Laura Holmes <holmes@google.com>
- Date: Wed, 11 Jul 2007 09:58:39 -0400
- To: "Roland Gülle" <roland@7val.com>
- Cc: public-mobileok-checker <public-mobileok-checker@w3.org>
- Message-ID: <135a9f560707110658u5d2cf0cfs614a139b2a44b50c@mail.gmail.com>
Sweet. Sounds good. As far as implementation, in order to get the line number, we're going to have to call an external java function. The java function needs the current node passed in as a parameter in order to obtain the line number stored in the node as an attribute. Here's two solutions: 1) to reduce code bloat - pass the current node to the result function. Within the results function we'll have to call the java function. 2) to reduce number objects passed between methods - call the java function from within the individual test and then pass the line number to the result function Either way, we can pass a null value into the results function in the case where we don't want to print a line number. I'm not entirely sure how xsl works as far as memory or the groups thoughts regarding either of the two issues mentioned above, but I'm tempted to advocate #1 just for clarity purposes. Cheers, Laura On 7/10/07, Roland Gülle <roland@7val.com> wrote: > > Laura, > > > Also, I'm still not quite sure what we determined about the > > position information format for error reporting. Roland, are you > > working on that? > No (sorry for this late feedback for this short feedback). > I try to add this feature at the weekend... > > Some ideas how this could be work: > - call the result template with a new parameter: > with-param name="position">true</ > ... return line position with the correct syntax > > Any ideas how the function should be work with the CSS check? > > Cheers, > Roland > >
Received on Wednesday, 11 July 2007 13:58:55 UTC