(PENDING) Strange formatting in Firefox
Discussion
B'stard Child said:
The bit in bold - I kinda get it but surely if you gave people a heads up you wouldn't get a bunch of different threads started with this has gone squiffy is it my PC or PH - several threads I've looked at today have had formatting issues raised and they haven't been in website feedback
Nice point there... that's surely a better argument... I will make sure to raise it with the team...Quick question, do you think that by giving a heads up would reduce the amount of complaints outside website feedback? (just trying to come up with questions that will be raised and I will have to answer to
)tirolo_ said:
Hi can I please get your user agent please? You can get it from google by searching for: "what's my user agent"... I'm guessing is the same issue as above
Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.96 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
Mozilla/5.0 (Android 9; Mobile; rv:67.0) Gecko/67.0 Firefox/67.0
Android 9 on a Huawei Mate 20 Pro
On Chrome where it works ok it is:
Mozilla/5.0 (Linux; Android 9; LYA-L09) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.101 Mobile Safari/537.36
Android 9 on a Huawei Mate 20 Pro
On Chrome where it works ok it is:
Mozilla/5.0 (Linux; Android 9; LYA-L09) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.101 Mobile Safari/537.36
Edited by karma mechanic on Wednesday 26th June 15:30
tirolo_ said:
B'stard Child said:
The bit in bold - I kinda get it but surely if you gave people a heads up you wouldn't get a bunch of different threads started with this has gone squiffy is it my PC or PH - several threads I've looked at today have had formatting issues raised and they haven't been in website feedback
Nice point there... that's surely a better argument... I will make sure to raise it with the team...Quick question, do you think that by giving a heads up would reduce the amount of complaints outside website feedback? (just trying to come up with questions that will be raised and I will have to answer to
)https://www.pistonheads.com/gassing/topic.asp?h=0&...
Snapshot
Although I expected it to be OK now and it isn't so maybe not related......
But that just raises the point that when formating or functionality goes a bit pete tong - it tends to be noticed in the thread it happened in and commented on that thread - it's only if it's persistant or frankly bloody annoying that a few people reach for Website Feedback
B'stard Child said:
I could link to the threads if I had time but here's a good example of just one I saw in NP&E
https://www.pistonheads.com/gassing/topic.asp?h=0&...
Snapshot
Although I expected it to be OK now and it isn't so maybe not related......
But that just raises the point that when formating or functionality goes a bit pete tong - it tends to be noticed in the thread it happened in and commented on that thread - it's only if it's persistant or frankly bloody annoying that a few people reach for Website Feedback
Some valuable info there! Just learned a lot from you thanks for that! I will make sure to share the knowledge with the team and define some actions to get things moving!https://www.pistonheads.com/gassing/topic.asp?h=0&...
Snapshot
Although I expected it to be OK now and it isn't so maybe not related......
But that just raises the point that when formating or functionality goes a bit pete tong - it tends to be noticed in the thread it happened in and commented on that thread - it's only if it's persistant or frankly bloody annoying that a few people reach for Website Feedback
tirolo_ said:
Some valuable info there! Just learned a lot from you thanks for that! I will make sure to share the knowledge with the team and define some actions to get things moving!
No probsIf PH HQ doesn't want to share publicly any development work going live you could always use the control board - to share with a smaller active group
https://www.pistonheads.com/gassing/forum.asp?h=0&...
It not like it's being used for anything else
Managed to finally have a look on this... I was hoping it was related to some recent changes to how we do device detection but it isn't meaning we will need to allocate resources to dig deep down and find/fix the issue so if you are still experiencing this please let us know and we will prioritise accordingly.
Alright, while I personally agree this is frustrating I'm trying to make a case so resources can be allocated but after looking at the usage data the amount users affected are less than 0.2% so I we can expect the priority will be accordingly.
I know and agree it's far from ideal not being able to use our favourite browser to navigate around on PH (or any website for that matter) and all the new stuff we are creating we are making sure to bear that in mind, but when it comes to fix legacy code we need to look into data to drive our priorities, that said, as things are right now, if you want to have a more supported experience I would have to suggest using a more supported browser like Chrome/Safari.
Sorry for the inconvenience this is causing, I hope we will be able to get this fixed soon.
For transparency sake, and in case anyone cares , this is related to the poor implementation we have in device detection (yes we have a bunch of adaptive stuff, yes we are moving into responsive instead) which is also causing a whole bunch of other problems to us, meaning although this specific issue only affect about 0.2% of the users there's still hope will get fixed soon as the other issues should help raise the priority for this.
Hope this gets things clearer and sets good expectations for the future, thanks again all for the great feedback and keep'em coming!
Regards!
I know and agree it's far from ideal not being able to use our favourite browser to navigate around on PH (or any website for that matter) and all the new stuff we are creating we are making sure to bear that in mind, but when it comes to fix legacy code we need to look into data to drive our priorities, that said, as things are right now, if you want to have a more supported experience I would have to suggest using a more supported browser like Chrome/Safari.
Sorry for the inconvenience this is causing, I hope we will be able to get this fixed soon.
For transparency sake, and in case anyone cares
, this is related to the poor implementation we have in device detection (yes we have a bunch of adaptive stuff, yes we are moving into responsive instead) which is also causing a whole bunch of other problems to us, meaning although this specific issue only affect about 0.2% of the users there's still hope will get fixed soon as the other issues should help raise the priority for this.Hope this gets things clearer and sets good expectations for the future, thanks again all for the great feedback and keep'em coming!
Regards!
tirolo_ said:
Alright, while I personally agree this is frustrating I'm trying to make a case so resources can be allocated but after looking at the usage data the amount users affected are less than 0.2% so I we can expect the priority will be accordingly.
So it's only affecting Firefox users From here https://en.wikipedia.org/wiki/Web_browser
| Browser | User % |
| Google Chrome | 72.40% |
| Mozilla Firefox | 9.10% |
| Internet Explorer | 5.40% |
| Safari | 5.10% |
| Microsoft Edge | 4.00% |
| Opera | 2.20% |
| UC Browser | 0.55% |
| Yandex Browser | 0.39% |
| C?c C?c | 0.20% |
| Chromium | 0.15% |
| Sogou Explorer | 0.14% |
| QQ Browser | 0.13% |
| Maxthon | 0.08% |
| Mozilla Suite | 0.05% |
| Vivaldi | 0.04% |
| 360 Secure Browser | 0.02% |
| Naver Whale | 0.02% |
| Pale Moon | 0.02% |
| mCent Browser | 0.02% |
| SeaMonkey | 0.01% |
| Other | 0.06% |
Where do you get the 0.2% from?
tirolo_ said:
I know and agree it's far from ideal not being able to use our favourite browser to navigate around on PH (or any website for that matter) and all the new stuff we are creating we are making sure to bear that in mind, but when it comes to fix legacy code we need to look into data to drive our priorities, that said, as things are right now, if you want to have a more supported experience I would have to suggest using a more supported browser like Chrome/Safari.
I started with netscape navigator (maybe giving my age away) so over the years I've used a lot of browsers but I stick with FF because I like it tirolo_ said:
Sorry for the inconvenience this is causing, I hope we will be able to get this fixed soon.
For transparency sake, and in case anyone cares , this is related to the poor implementation we have in device detection (yes we have a bunch of adaptive stuff, yes we are moving into responsive instead) which is also causing a whole bunch of other problems to us, meaning although this specific issue only affect about 0.2% of the users there's still hope will get fixed soon as the other issues should help raise the priority for this.
So if it's poor implementation of device detection how do you know you 0.2% of users is correct For transparency sake, and in case anyone cares
, this is related to the poor implementation we have in device detection (yes we have a bunch of adaptive stuff, yes we are moving into responsive instead) which is also causing a whole bunch of other problems to us, meaning although this specific issue only affect about 0.2% of the users there's still hope will get fixed soon as the other issues should help raise the priority for this.tirolo_ said:
Hope this gets things clearer and sets good expectations for the future, thanks again all for the great feedback and keep'em coming!
Regards!
Any feedback is good feedback even if it's not the news that some of us wantRegards!
Gassing Station | Website Feedback | Top of Page | What's New | My Stuff