Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when "noRecTrack" is used #367

Closed
iherman opened this issue Dec 6, 2014 · 2 comments
Closed

Error when "noRecTrack" is used #367

iherman opened this issue Dec 6, 2014 · 2 comments
Labels

Comments

@iherman
Copy link
Member

iherman commented Dec 6, 2014

If, in a WG Draft (this was a FPWD, if that counts) the

noRecTrack:           "false",

is used then generated status section still includes:

The group does not expect this document to become a W3C Recommendation.

in the paragraph on patent disclosures, and does not include the

This document is intended to become a W3C Recommendation.

elsewhere in the status section. It looks as if the presence of the flag is what counts and not its value. (this is in contrast with what the manual says)

Ivan

@iherman iherman added the bug label Dec 6, 2014
@halindrome
Copy link
Contributor

I actually think the problem is that you put false in quotation marks. false is a boolean value in Javascript. When it is not in quotes the feature works as expected. A value in quotation marks is evaluated as true.

@iherman
Copy link
Member Author

iherman commented Dec 10, 2014

On 10 Dec 2014, at 16:12 , Shane McCarron notifications@github.com wrote:

I actually think the problem is that you put false in quotation marks. false is a boolean value in Javascript. When it is not in quotes the feature works as expected. A value in quotation marks is evaluated as true.

Ouch. :-)

Ivan


Reply to this email directly or view it on GitHub.


Ivan Herman, W3C
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704

shikhar-scs pushed a commit to shikhar-scs/respec that referenced this issue Feb 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants