Re: [Interest] Did QUrlQuery::queryItemValue change its decoding behaviour in 5.2-beta1?

2013-11-07 Thread Philipp Kursawe
Thanks, I found the commit before, but missed that it also changed decoding of :// On Thu, Nov 7, 2013 at 6:50 PM, Thiago Macieira wrote: > On quinta-feira, 7 de novembro de 2013 14:02:06, Philipp Kursawe wrote: > > My code just broke when I wanted to use the return value of > > requestQuery.que

Re: [Interest] Did QUrlQuery::queryItemValue change its decoding behaviour in 5.2-beta1?

2013-11-07 Thread Thiago Macieira
On quinta-feira, 7 de novembro de 2013 14:02:06, Philipp Kursawe wrote: > My code just broke when I wanted to use the return value of > requestQuery.queryItemValue("redirect_uri"); > > and expected it to be "schema://authorized" (as in <5.2) but instead got it > back as undecoded value. > > So ha

[Interest] Did QUrlQuery::queryItemValue change its decoding behaviour in 5.2-beta1?

2013-11-07 Thread Philipp Kursawe
My code just broke when I wanted to use the return value of requestQuery.queryItemValue("redirect_uri"); and expected it to be "schema://authorized" (as in <5.2) but instead got it back as undecoded value. So has the default behaviour changed? I couldn't find anything in the commit history about