Liam Quin

I'd far rather use document.evaluate("//comment()") (i.e. XPath) for this case, as it's much more readable even for people who don't like XPath or are allergic to the letter x :-)...

using constants is massively better than "8" :) and also better than strings (because a typo will always fail). But does this really add so much compared to existing methods?

I do not dispute the benefits of being able to write, tbody/tr/th[contains(., "Esterhazy")]/following-sibling::th[2] - i do this on a daily basis. I didn't need to write a new method to...

> @liamquin The goal of this method is to attain a list of nodes of the request type from descendant nodes _irrespective of additional specificity_. An XPath instance requires a...

@annevk XPath 2 (and, more to the point these days, 3.1) are highly backward compatible with XPath 1. There _are_ some differences. Example: in XPath 1, the string value of...

Rendering a claim would involve additional items in the dm i think, to mark natural language (and there are security implications, making sure the text alternative is a correct translation).

Why not rewrite //p[text() contains text 'popular'] as //p[text()[. contains text 'popular']] would it then use the index?? Or, betterr maybe, text()[. contains text 'popular']/..[self::p] ?

This could be a win for accessibility (and monetization/conversion) for inserted adverts, where e.g. the user has specified a larger minimum text size than the default, but at the expense...

A fix is to change it to use gnome shell as a fallback: else: output = os.popen("gnome-session --version") result = output.readlines() if len(result) < 1: output = os.popen("gnome-shell --version") result...

An alternative might be to support changing the pallette on a per-line bases, so highlighting could change the result of resetting to colour zero.