RESOLVED INVALID106234
Setting font style crashes wxWebKit with jQuery Mobile 
https://bugs.webkit.org/show_bug.cgi?id=106234
Summary Setting font style crashes wxWebKit with jQuery Mobile
George Henne
Reported 2013-01-07 10:58:59 PST
Created attachment 181534 [details] Python + HTML code Python: import wx import wx.webview app = wx.App(redirect=False) frame = wx.webview.WebBrowserShell('wxWebKit Test') frame.Show() app.MainLoop() HTML: <!DOCTYPE HTML> <html> <head> <link rel="stylesheet" href="http://code.jquery.com/mobile/1.2.0/jquery.mobile-1.2.0.min.css" /> <script src="http://code.jquery.com/jquery-1.8.2.min.js"></script> <script src="http://code.jquery.com/mobile/1.2.0/jquery.mobile-1.2.0.min.js"></script> <style type="text/css"> // the name of the font or its existence does not matter @font-face {font-family: xxx; src: url('xxx.ttf');} </style> </head> <body> <input type=text style="font-family:xxx;" value="This is xxx Font." /> </body> </html>
Attachments
Python + HTML code (818 bytes, application/x-zip-compressed)
2013-01-07 10:58 PST, George Henne 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
George Henne
Comment 1 2013-01-07 11:14:14 PST
The HTML can actually be made shorter - only jQuery is needed: <!DOCTYPE HTML> <html> <head> <style type="text/css"> @font-face {font-family: xxx; src: url('xxx.ttf');} </style> </head> <body> <input type=text style="font-family:xxx;" value="This is xxx Font." /> </body> </html>
George Henne
Comment 2 2013-01-07 11:23:11 PST
Sorry - too enthusiastic with my deletions! <!DOCTYPE HTML> <html> <head> <script src="http://code.jquery.com/jquery-1.8.2.min.js"></script> <style type="text/css"> // the name of the font or its existence does not matter @font-face {font-family: xxx; src: url('xxx.ttf');} </style> </head> <body> <input type=text style="font-family:xxx;" value="This is xxx Font." /> </body> </html>
Alexey Proskuryakov
Comment 3 2023-02-03 08:37:30 PST
Mass closing remaining WebKit wx bugs, as this port is long gone.
Note You need to log in before you can comment on or make changes to this bug.