Used URL and RegExp are as follows, and they work well in RainRegExp testing/parsing with no problem.
Code: Select all
URL=https://weather.com/forecast/allergy/l/(Location Code)
RegExp=(?siU).*Pollen Breakdown.*Tree Pollen.*</circle></svg></div>(.*): <strong>(.*)</strong>.*</circle></svg></div>(.*): <strong>(.*)</strong>.*</circle></svg></div>(.*): <strong>(.*)</strong>.*Grass Pollen.*</circle></svg></div>(.*): <strong>(.*)</strong>.*</circle></svg></div>(.*): <strong>(.*)</strong>.*</circle></svg></div>(.*): <strong>(.*)</strong>.*Ragweed Pollen.*</circle></svg></div>(.*): <strong>(.*)</strong>.*</circle></svg></div>(.*): <strong>(.*)</strong>.*</circle></svg></div>(.*): <strong>(.*)</strong>.*
However, oh however... when I leave the failed skin working as it is, after one or two updates of the WebParser measure, the html feed suddenly becomes "for desktop device" as expected, so the measure returns right results. I did actually nothing at all, no deletion of IE cookies.
At the next load/refresh, obtained html source is "for mobile" again, and after update, it becomes "for desktop" again and everything is OK again... Really weird mystery possibly caused by the discretion of Weather.com's web engineer.
So, to avoid this glitch (for me), I temporarily set the mouse action as [!CommandMeasure (WebParser measure name) Update] to a button. This solves the issue manually and even instantly.
Anyone encountered such odd behavior of weather.com and WebParser measure?!
Sorry if this is a "well-known and needless-to-say" issue.