HI, I cant carry on with
as it was closed.
But the problem persists.
so for instance.
On the very first opening of a URL.
PG correctly finds a single fault.
Divs within a Span - semantic/structural error.
but then if you make ANY change and save it, even to include simply syntax errors, ie, just including a space
in
sp an
it passes as fine in the pop up error checking, while the code editor blows up with warning symbols.
they are incongruous and don’t tally, so which one of them is correct?
So the original structural error persists, which was correctly picked up by PG parser, plus one new syntax error, but it all now passes as fine and the original error which WAS initially picked up, no longer is.
which one to believe?
Code editor or error checking modal pop up window.
If not the latter then its not much use really is it 
As that is its actual purpose.
It would be nice if they both reflected each other
NOTE!
if i remove the space in sp an
the error check from menu
no longer flags the initial error.
Page→check page for html errors
So why does it pick it up initially, then fail to when refreshed but the code is reverted to original, containing only the initial error, which it once flagged up and no longer is able too?
It’s as though its checking some other saved state of the page, or other previously corrected page in the project/its cache or not actually refreshing its error check at all when you click the blue refresh button.
Cheers.
Great on the new PG9 btw and Happy New Year.