SuttaCentral: bug reports

[agilgur5]

@agilgur5

EDIT: Actually, this works correctly for me, it’s just that the number is at the very top of the screen, obscured by the top nav bar, which makes the next number often show up in the middle.

I also confirmed that the anchor link is the correct number.
This is browser behavior, so this is difficult/finicky to change - you’d have to detect an anchor movement and scroll it a bit further up or move the anchor a few lines up. And the vertical distance may be different depending on your Views settings, as well as your device width.
Might be a “won’t fix” as such

And I recently learned there’s a CSS property to handle this: scroll-margin-top. Baseline available since 2021, so my grays are showing a bit not having known that.

I feel like this should be added to every anchor tag though, so I’m not sure what the appropriate place for that style is – will leave it to @HongDa then

---

EDIT:

Also got some more missing localization warnings while testing:

missing translation key viewoption:ptsRefsEnabled
missing translation key viewoption:ptsRefsDisabled

and indeed those don’t seem to exist in bilara-data

---

EDIT2:

@Snowbird

It looks like the individual edition pages don’t have proper page titles?

For this particular page, HongDa had a PR to improve this last year: Fixed title and style issues on publication pages. by ihongda · Pull Request #3492 · suttacentral/suttacentral · GitHub

But it seems to still be the case on certain pages, like https://suttacentral.net/edition/pli-tv-vi/brahmali/bu-vb-1-introduction/bi-vb-introduction, gives me publicationEditionMatter—SuttaCentral with the default meta description as well.
It also seems to glitch out and stop updating titles if I click on enough ones without them.

The generic code for this tries to localize the route name, but there is no localization for interface:publicationEditionMatter.
HongDa’s PR above gave a more specific metadata path for the publication-edition component, but not the publication-edition-matter component, which could probably use a very similar PR