Price chart with slider is invisible
Categories
(Firefox for Android :: Browser Engine, defect)
Tracking
()
People
(Reporter: u724759, Unassigned)
Details
User Agent: Mozilla/5.0 (Android 13; Mobile; rv:121.0) Gecko/121.0 Firefox/121.0
Steps to reproduce:
I went on any price history website (such as, for example: geizhals.de, idralo.de, keepa.com, camelcamelcamel.com)
When wanting to see the price history with the diagram, it is invisible.
Actual results:
When wanting to see the price history with the diagram, it is invisible. When sliding on it with my finger however, the information is shown (except the diagram)
Expected results:
Normal display of the graph/chart.
Comment 1•1 year ago
|
||
Could you provide more steps to reproduce, or perhaps a screenshot or video of the bug? When visiting a product on camelcamelcamel I am able to see the price history graph on my S22.
Updated•1 year ago
|
(In reply to Jeff Boek [:boek] from comment #1)
Could you provide more steps to reproduce, or perhaps a screenshot or video of the bug? When visiting a product on camelcamelcamel I am able to see the price history graph on my S22.
Yeah I will update you asap. The problem is that it sometimes works and sometimes dont.
(In reply to Jeff Boek [:boek] from comment #1)
Could you provide more steps to reproduce, or perhaps a screenshot or video of the bug? When visiting a product on camelcamelcamel I am able to see the price history graph on my S22.
So now the bug occurred again.
Down below I uploaded a screen recording where I show the bug happening. I couldn't find out how those website elements are called, so I couldn't do any research or testing on that. Could someone tell me what those elements are called?
I tried to find a few websites but I couldn't think of that many websites . I also went to two html and css test sites but idk if they are relevant in this case.
Link to Videos and screenshots:
https://gofile.io/d/k1M8GE
Comment 4•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Fenix::Browser Engine' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Description
•