Closed iherman closed 6 years ago
To make the possible discussion here simpler and not forcing to go back to other issues, the changes are:
name
entry for the document (a.k.a. title) is a required elementname
is not specified in the (authored) manifest, the content of the title
element in the primary entry page is used instead. This is done via the step in the canonical manifest.Also, the term "as a non-zero title element" is a mystery for me. I believe it means non empty, but ...
Also, the term "as a non-zero title element" is a mystery for me. I believe it means non empty, but ...
It is also a mystery for me:-) Changed it to non empty
@llemeurfr
allow an empty title in the manifest
I am fine with this. (I am not sure how this statement got into the draft in the first place.)
However, one step further then: the heuristics the UA can use if neither the name
nor the title
is present may also include explicitly the possibility to use an empty name
. Although that section is not really normative, I guess it is better to make this explicit. WDYT?
Well, we can consider that if the author explicitly sets an empty title (using an empty name in manifest + empty html title), he lets in practice the UA do its way. I would say that if the UA decides to keep an empty title, yes it can. But in this case, the item will not appear properly in a list of publications handled by the UA, therefore it is bad practice and should not be encouraged.
@llemeurfr you convinced me:-) I removed the reference to an emtpy title.
@llemeurfr @TzviyaSiegman @wareid @mattgarrish is it o.k. to merge this?
Adopted wording in https://github.com/w3c/wpub/pull/331#issuecomment-436199708. That comment is a proposal to close a long-standing issue.
Fix #325
Replaces #331 (and closing that one)
Preview | Diff