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

Draft: SC2-2-1+SC3-2-5-meta-refresh #111

Merged
merged 1 commit into from
May 14, 2018

Conversation

annethyme
Copy link
Collaborator

No description provided.

@jeeyyy jeeyyy changed the title SC2-2-1+SC3-2-5-meta-refresh Draft: SC2-2-1+SC3-2-5-meta-refresh Apr 30, 2018

### Applicability

The rule applies to any `content` attribute in a `meta` element that contains the `http-equiv` attribute with value `"refresh"` (case-insensitive).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mention element before attribute.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@WilcoFiers: Right now the rule applies to the content attribute. Your suggested change will make the rule apply to the meta element. Is this what we want?

If yes, I suggest changing it into this:
The rule applies to any meta element that contains the http-equiv attribute with value "refresh" (case-insensitive) and that also has a content attribute .

Copy link
Collaborator

@cpandhi cpandhi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good.

@jeeyyy jeeyyy merged commit 17b3b6e into master May 14, 2018
@jeeyyy jeeyyy deleted the drafts-SC2-2-1+SC3-2-5-meta-refresh branch May 14, 2018 08:21
@jeeyyy
Copy link
Collaborator

jeeyyy commented May 14, 2018

Final PR - #133

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants