Ce sujet a été marqué résolu par son auteur, le 7 Octobre 2012 à 17:48
« Attachment handler bug
Drafts being saved is not shown in QR
In passing... »

Arantor

  • As powerful as possible, as complex as necessary.
  • Messages: 14 278
Re: Drafts being saved is not shown in QR
« Réponse #15, le 28 Avril 2012 à 01:43 »
Yeah, IE supports that but others don't >_<

I think we'll have to deal with this on a case by case basis in the JS, really, and just look for cases where we manually push ;xml onto the URL from JS where we might not otherwise.
When we unite against a common enemy that attacks our ethos, it nurtures group solidarity. Trolls are sensational, yes, but we keep everyone honest. | Game Memorial

live627

  • Should five per cent appear too small / Be thankful I don't take it all / 'Cause I'm the taxman, yeah I'm the taxman
  • Messages: 1 670
A confident man keeps quiet.whereas a frightened man keeps talking, hiding his fear.

Nao

  • Dadman with a boy
  • Messages: 16 082
Re: Drafts being saved is not shown in QR
« Réponse #17, le 28 Avril 2012 à 10:36 »
Ah, the human spammers...

Anyway, Pete -- I checked all ;xml additions, and apart from ajaxRating (which always deals with a long URL that has no chance to fail), it'll always use weUrl()/we_prepareScriptUrl() as a basis anyway.
Ah ah, found a way to get rid of my .charAt... Using .match instead :) (or .test, FWIW... Same bytesize results. Saves over 10 bytes compared to the charAt version, and this in just one line of code, eh...)

Arantor

  • As powerful as possible, as complex as necessary.
  • Messages: 14 278
« Attachment handler bug
In passing... »