Leading '.' in `classList.add` or `classList.remove`
User guide
- Getting Started
Api
Concepts
Configurations
Configuring webhint
Connectors
Development flow integration
Extensions
Formatters
Hints
- Avoid CSS limits
- Avoid HTTP redirects
- axe accessibility check
- Babel configuration hint set
- Compatibility of CSS, HTML and JavaScript features
- Correct `Content-Type` header
- Correct manifest extension
- Correct viewport
- Detect CSS Reflows
- Disallowed HTTP headers
- External links disown opener
- Has web app manifest
- Highest document mode
- HTTP cache
- Leading '.' in `classList.add` or `classList.remove`
- Manifest has name
- Minify JavaScript
- Modern DOCTYPE
- No `createElement` with SVG
- No `P3P` headers
- No broken links
- No byte-order mark
- No Inline CSS Styles
- No protocol-relative URLs
- No small error pages
- No vulnerable libraries
- Nu HTML test
- Optimal compression
- Optimize images
- Performance budget
- Prefixed CSS first
- scoped-svg-styles
- Specify button type
- SSL server test
- TypeScript configuration hints set
- Unneeded HTTP headers
- Use `Strict-Transport-Security` header
- Use `X-Content-Type-Options` header
- Use Apple touch icon
- Use charset `utf-8`
- Use HTTPS
- Use subresource integrity
- Valid `Set-Cookie` header
- Valid `theme-color`
- Valid manifest
- webpack configuration hints set
Parsers
Server configurations
Troubleshoot
- Api
- Concepts
- Configurations
- Configuring webhint
- Connectors
- Development flow integration
- Extensions
- Formatters
- Hints
- Parsers
- Server configurations
- Troubleshoot
Leading ‘.’ in classList.add
or classList.remove
This hint informs users that they should to use
Element.classList
argument without a leading ‘.’ as it
may lead to unintended results.
Why is this important?
When writing selectors either in CSS or using DOM methods like
querySelector
, class names are referred to using a leading ‘.’,
e.g. document.querySelector('.foo')
. However when modifying the
classList
of an element the raw class name is expected to be used
instead, e.g. element.classList.add('foo')
.
Unfortunately if a leading ‘.’ is provided to the classList
APIs
it will succeed without an error, treating the ‘.’ as part of the
name itself. This typically causes selectors elsewhere in the code
to fail to match this element. Figuring out why can be tedious and
time-consuming until the typo has been found.
What does the hint check?
This hint scans JavaScript source code to check if the argument in
element.classList.add
or element.classList.remove
contains a
leading ‘.’. If so it emits a warning to help save time debugging
this subtle issue.
Examples that trigger the hint
const element = document.getElementById('foo');
element.classList.add('.foo');
element.classList.remove('.foo'); |
Examples that pass the hint
const element = document.getElementById('foo');
element.classList.add('foo');
element.classList.remove('foo'); |
How to use this hint?
This package is installed automatically by webhint:
npm install hint --save-dev |
To use it, activate it via the .hintrc
configuration file:
{
"connector": {...},
"formatters": [...],
"parsers": [...],
"hints": {
"leading-dot-classlist": "warning"
},
...
} |
Note: The recommended way of running webhint is as a devDependency
of
your project.