I find this rather frustrating. I would prefer the default be to NOT have that feature and be able to add true to enable it. The vast majority of the time, I am displaying stored information that has been vetted, and would only want this protection on occasion. Using the bindings tab does not include a parameter, so I have to add it with nearly every insertion.
I can customize it in rsobj.php, but then any extension update or perhaps (I have not tested), will wipe out the change.
I would like to see a way to change the default behavior at instantiation.
perhaps adding it to the construct function like:
public function __construct($name,$conn,$maxRows=0,$hardLimit=false,$crossSiteProtect=true) {
...$this->CrossSiteProtect = $crossSiteProtect;
Actually, make that
public function __construct($name,$conn,$maxRows=0,$crossSiteProtect=true,$hardLimit=false) {
...$this->CrossSiteProtect = $crossSiteProtect;
because I think the CSP would be changed more often.
Alternatively a setter method to add to the RS code like:
$rs = new WA_MySQLi_RS("events",$conn_i,0);
$rs->CrossSiteProtect(false);