a8d4a8aa52
Previously, any unpaired quote in the text selector "escaped" everything till the end of the selector string, and so any subsequent chained selectors, including ">>" separator were ignored. An example of misbehaving selector: `text=19" >> nth=1`. Now, when text selector contains a non-leading quote, selector parser does not assume it should escape ">>" separator and correctly tokenizes all selectors from the chain. Note that this behavior is a workaround for the fact that our text selectors is somewhat poorly defined in this area. That said, this workaround seems to be safe enough. It still does not work for unpaired leading quotes like this: `text="19 >> nth=1`. |
||
|---|---|---|
| .. | ||
| cli | ||
| client | ||
| common | ||
| dispatchers | ||
| grid | ||
| protocol | ||
| remote | ||
| server | ||
| third_party | ||
| utils | ||
| browserServerImpl.ts | ||
| DEPS | ||
| inprocess.ts | ||
| inProcessFactory.ts | ||
| outofprocess.ts | ||