You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's say it removes part .second-elem from the selector and full selector still works fine, then it tries to remove the second class too, which creates incorrect selector like that: .first-elem > >.last-elem which cause an error when calling this line
When some specific element have few classes in the selector, then optimization cause an error.
For example,
Let's say that full path looks like that:
.first-elem >.second-elem.another-class >.last-elem
When
optimizePart
called with following arguments:So when class optimisation starts to work
optimal-select/src/optimize.js
Line 125 in 722d220
Let's say it removes part
.second-elem
from the selector and full selector still works fine, then it tries to remove the second class too, which creates incorrect selector like that:.first-elem > >.last-elem
which cause an error when calling this lineoptimal-select/src/optimize.js
Line 135 in 722d220
The text was updated successfully, but these errors were encountered: