AaronX Posted May 22, 2018 Report Share Posted May 22, 2018 When a page has an apostrophe in the <title>, it becomes corrupted with a wide extra space in the tab name. I've observed this on multiple sites over the last few Windows releases, both beta and final. Link to comment Share on other sites More sharing options...
BugSir006 Posted May 30, 2018 Report Share Posted May 30, 2018 Dear Aaron, Thanks for feedback! We will check and feedback Link to comment Share on other sites More sharing options...
BugSir006 Posted June 1, 2018 Report Share Posted June 1, 2018 Hi, Aaron We tested on Chrome Firefox, they all displayed as the screenshot you provided us. It should be the website itself displayed abnormally. Link to comment Share on other sites More sharing options...
AaronX Posted June 8, 2018 Author Report Share Posted June 8, 2018 On 6/1/2018 at 9:06 AM, BugSir006 said: Hi, Aaron We tested on Chrome Firefox, they all displayed as the screenshot you provided us. It should be the website itself displayed abnormally. Do you mean that Chrome and Firefox also display the big space, and thus it must be a website issue? I've found the same behaviour on multiple websites and on inspecting the code, none of the <title> tags have any big odd gaps in - so it must be a wider WebKit bug. Link to comment Share on other sites More sharing options...
AaronX Posted June 17, 2018 Author Report Share Posted June 17, 2018 https://www.thetimes.co.uk/article/3a8383be-70eb-11e8-bea3-bf1a5a054f3a <title>Brexiteers handed NHS ‘victory’ with strings attached | News | The Times</title> See screenshots for the same page in Maxthon and Chrome. MX renders with the erroneous spaces, Chrome does not. Link to comment Share on other sites More sharing options...
MaxthonJeff Posted June 19, 2018 Report Share Posted June 19, 2018 Chrome displays the same space as Maxthon on my system. Can anybody else confirm ? ??Set your payment address in profile if you have not. Let's reward people who contribute to Maxthon community. ❤️❤️ Click Here ❤️❤️ Link to comment Share on other sites More sharing options...
7twenty Posted June 19, 2018 Report Share Posted June 19, 2018 I'm pretty sure it's due to the different font that's being used. I tested with an older version of Chrome, and get the same as AaronX. If i'm not mistaken MX uses MS YaHei in most of the UI, I think Chrome uses Arial, or something similar. Using the same text copied from Notepad into MS Word: It's something related to the spacing of some of the special characters. It's not a fixed width font, but the spacing of the special characters seems to be double what it should be. Changing the UI font to use MS Yahei UI, instead of the base version should fix the issue as shown above. Link to comment Share on other sites More sharing options...
AaronX Posted June 19, 2018 Author Report Share Posted June 19, 2018 I think you've probably diagnosed that correctly, 7twenty. There's a very subtle difference in the fonts used in each browser that I've only just noticed; and Jeff's Chrome screenshot appears to use the same font as my MX one. (Note the dot above the i, which appears to be a single pixel in my Chrome screenshot but 2 pixels vertically in Jeff's Chrome and my MX.) I can't see a way to change my MX font, or to set Chrome to YaHei in order to test that specifically, however. Link to comment Share on other sites More sharing options...
7twenty Posted June 19, 2018 Report Share Posted June 19, 2018 4 hours ago, AaronX said: I can't see a way to change my MX font, or to set Chrome to YaHei in order to test that specifically, however. There isn't. It needs to be changed in the UI files. It's a simple fix, so there's no reason why they shouldn't get it done before the next release... But no guarantee that it will happen then, or any time after that... Link to comment Share on other sites More sharing options...
7twenty Posted June 19, 2018 Report Share Posted June 19, 2018 This is what it looks like when the correct font (YaHei UI) is set in the UI files. Link to comment Share on other sites More sharing options...
7twenty Posted July 2, 2018 Report Share Posted July 2, 2018 A little disappointing that after 2 more releases (final and a new beta), this still isn't fixed. It's a very minor issue, sure, but it also has the simplest fix you can get - it's literally adding " UI" to the fonts section in the UI files! Just 3 characters! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.