Public bug reported:
Not sure if this is a bug or i'm doing something wrong.
In Dekko when trying to set the charset like
QNetworkReply::setHeader(QNetworkRequest::ContentTypeHeader,
QString("text/html; charset=utf-8")) the page get's rendered as the raw
html (See the attached image). So the charset has to be omitted in order
to display the formatted content.
The Qt docs imply i am correct in trying to set the charset this way. Is
there some other way i'm supposed to do this with Oxide's
QNetworkAccessManager bridge?
Cheers
Dan
** Affects: oxide
Importance: Undecided
Status: New
** Attachment added: "rawhtml.png"
https://bugs.launchpad.net/bugs/1569231/+attachment/4633839/+files/rawhtml.png
** Description changed:
Not sure if this is a bug or i'm doing something wrong.
In Dekko when trying to set the charset like
QNetworkReply::setHeader(QNetworkRequest::ContentTypeHeader,
- QString("text/html, charset=utf-8")) the page get's rendered as the raw
+ QString("text/html; charset=utf-8")) the page get's rendered as the raw
html (See the attached image). So the charset has to be omitted in order
to display the formatted content.
The Qt docs imply i am correct in trying to set the charset this way. Is
there some other way i'm supposed to do this with Oxide's
QNetworkAccessManager bridge?
Cheers
Dan
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1569231
Title:
Not able to set charset in QNetworkReply header for custom url schemes
Status in Oxide:
New
Bug description:
Not sure if this is a bug or i'm doing something wrong.
In Dekko when trying to set the charset like
QNetworkReply::setHeader(QNetworkRequest::ContentTypeHeader,
QString("text/html; charset=utf-8")) the page get's rendered as the
raw html (See the attached image). So the charset has to be omitted in
order to display the formatted content.
The Qt docs imply i am correct in trying to set the charset this way.
Is there some other way i'm supposed to do this with Oxide's
QNetworkAccessManager bridge?
Cheers
Dan
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1569231/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
