Gotcha, sorry for misunderstanding.
> I view the statement using Firefox browser, and everything looks fine.
So, *this* is the part where I'm hoping you might be able to do "File | Save As", and choose "Web Page, Complete" -- would you mind trying that? I'm guessing that when you tried File|Save before, it was when you were viewing the broken PDF, which is why the save dialog only offered you PDF options.
Same request for the font devtools -- I'm not sure if your previous response about the fonts were when you were viewing the website vs. the broken PDF, but I'm wanting to know the fonts that the website uses for the elements in question (in the interests of perhaps being able to recreate the problem locally.)
Thanks!
Bug 1896915 Comment 11 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Gotcha, sorry for misunderstanding.
> I view the statement using Firefox browser, and everything looks fine.
So, *this* is the part where I'm hoping you might be able to do "File | Save As", and choose "Web Page, Complete" -- would you mind trying that? (and then seeing if the resulting saved HTML still reproduces the bug; hopefully it does)
I'm guessing that when you tried File|Save before, it was when you were viewing the broken PDF, which is why the save dialog only offered you PDF options.
Same request for the font devtools -- I'm not sure if your previous response about the fonts were when you were viewing the website vs. the broken PDF, but I'm wanting to know the fonts that the website uses for the elements in question (in the interests of perhaps being able to recreate the problem locally.)
Thanks!