Re: [widgets] P&C: Step 8 bug when custom start file is bogus

On Mon, Oct 5, 2009 at 2:13 PM, Arthur Barstow <art.barstow@nokia.com> wrote:
> Marcos, All,
>
> During the processing of <content> in Step 7, if the custom start file is
> bogus (and the spec indicates a few reasons why it could be bogus), "widget
> start file" will be null when the UA completes Step 7. In this case, we
> presumably want the UA to run all of Step 8, in particular "algorithm to
> locate a default start file", in keeping with principle of least surprise,
> be forgiving, etc.
>
> However, when the UA then goes to Step 8:
>
> [[
> http://dev.w3.org/2006/waf/widgets/Overview_TSE.html#step-8--locate-the-start-file
>
> This step only applies if a custom start file was not specified in the
> configuration document (i.e., if widget start file of the table of
> configuration defaults is null).
>
> If widget start file of the table of configuration defaults contains a file,
> then a user agent must skip Step 8 and go to Step 9.
> ]]
>
> The first paragraph, as written, is broken and Step 8 will be skipped since
> a custom start file was specified. I think the first paragraph should be
> deleted and all that is needed is the 2nd paragraph, possibly with the
> additional parenthetical I add here:
>
> [[
> If widget start file of the table of configuration defaults contains a file
> (i.e. widget start file is not null), then a user agent must skip Step 8 and
> go to Step 9.
> ]]
>

Agreed. Paragraph 2 is more clear. Paragraph one has been deleted.
Added your text.


-- 
Marcos Caceres
http://datadriven.com.au

Received on Tuesday, 6 October 2009 10:25:25 UTC