Feedback - Bug Reports

Minor bug - when you complete your daily goal the message about extra study does not have the correct count of items studied for that deck in the current session.

For example:

  • Before doing lessons today I was on 192/217 items studied in N3.
  • I then did 2 lessons which after completion gives the daily goal completed message.
  • If you click extra study the deck selection is displayed, however the total items studied will not have increased for the decks studied.

So below, I was expecting the items studied for N3 to be 194/217, but it was still at 192/217. The Daily Goal counter is correct.

Can replicate on Android and Web App.

1 Like

They are now! :slight_smile:

1 Like

There’s a graphical glitch with the progress bar:

This is on Safari browser iOS (iPad).

This has been fixed. Thank you! :pray:

Nevermind. I thought it was, because the results page after reviews seems unaffected, but the other ones still are.

1 Like

Quite often the audio doesnt seem to work for me. It seems completely random whether or not it works, and if it doesnt work in the browser it also doesnt work in the app (ios). Is there a reason for this?

1 Like

In Vocab Search, there is the new feature where it shows you furigana for unknown kanji. Nice.

But, this came with two related bugs:

  1. You can no longer open the item in the browser by clicking anywhere on the item. Instead, if you click on any kanji portion of the item, it does not open the item’s page. This includes if I Ctrl-click to open in a separate tab.
    • This slows down opening several vocabs from the list because you have to be careful where you click, so as not to click on any kanji.
  2. When you do click on any kanji, it behaves like the old version of Bunpro where it will toggle whether to show the furigana for that kanji or not. I consider this a bug because:
    1. I don’t want random clicks in the search results to accidentally toggle furigana for some random kanji/word.
    2. The newer interface with the pop-up to manage furigana is better and more universal.

One of two solutions possible, IHMO:

  • Simply remove the toggle function from kanji in the search results, so clicking anywhere on the item opens it, as before.
  • Or, if ability to toggle within search results is intended as a feature (I’d be curious what kind of use case supports this? Maybe just ā€˜It always works the same way whenever you see furigana/kanji’? Is that the intention?), then at least use the newer pop-up interface to prevent accidental toggling, plus provide more control over that function/feature.

This accidental toggling thing has happened to me multiple times since I noticed the change, and I tried to ā€˜get used to it’, but I finally decided to post this as a bug report, since it is too annoying, and not as good as the pop-up control.

2 Likes

During a failed load of Reviews page, I got this:
Screenshot 2024-04-09 111658

Just pointing out that the Advanced Error Details is empty. Either the dialog did not fill in the advanced error details correctly, or there were no advanced details to show.

If the former, then that’s the bug.

But if the latter, then I’d suggest either disabling (greying out) the Advanced Error Details section (to keep the UI appearance the same, just with disabled elements), or to not show the Advanced Error Details section at all, when there are no extra details to show.

By indicating in the UI when there are no details to show, this at least allows us to distinguish between ā€˜no details’ and ā€˜failed to show details’ situations.

BTW: It’s quite likely that the failure was due to local WiFi weak signal. This report is just about the UI.

1 Like

Forgot to show this back when it happened, but I thought this was kinda funky lol.

1 Like

Thanks for the great bug report. I have fixed this and will include it with the next release. I have simply removed the toggle function completely because as you mentioned there isn’t really a use case for toggling furigana there.

3 Likes

Lots of vocab seems to have slipped back in terms of SRS, e.g. ā€œ ēˆ¶ę–¹ā€ is now back to Beginner 1. Pretty sure I didn’t get it wrong so much recently. There are many others too, like ā€œ åˆć€…ā€.

1 Like

It looks like it is set oddly. Did you remember if you reviewed it via the app or the website last time?

2 Likes

I think via the website!
Just bumped into ā€œę­¤å„“ā€ too, which is also back to Beginner 1. There seem to be a lot.

1 Like

Thanks! Just to narrow some things down, do you/have you used the app in the past to review it?

2 Likes

I don’t think so!
Just bumped into ā€œ ęœ‰ć‚‹ā€, ā€œć“ć†ć„ć†ā€ and ā€œé•·é“ā€, which have also fallen back.

1 Like

I am taking a look. I sent you a DM.

2 Likes

I’m experiencing a bug in the iOS app where I can’t remove words from my review. The pop up window comes up but both selecting cancel and remove don’t do anything. I have to kill the app to get the window to go away and the word doesn’t get removed.

2 Likes

Hey!
This bug has been fixed and will be released with next update!

Cheers!

3 Likes

Ok thanks for the fast response!

1 Like

There’s a bit of a bug / unexpected user flow with the Decks search.

If you are not logged in on bunpro.jp (main site), you can still access deck pages, for example bunpro.jp/decks/super/supercub
You can land there e.g. if you are logged in on community.bunpro.jp, or because the site logged you out automatically with a browser tab still open.

BUT, if you try to use the search box, nothing happens, and there’s no user-visible error message.
In the browser console you can see that GET https://bunpro.jp/decks/search?... returns a 500.

Perhaps some sort of user message that ā€œsearch doesn’t work because you are not logged inā€ would be helpful.
Or otherwise, redirecting to the login page from the deck page when not logged in.

1 Like

This is more of a systemic thing than just a single bug.

I just noticed that some Vocab items are accessible from more than one ā€˜official’ URL. For example, the Vocab for Hokkaido is accessible from these 2 different URLS:

  1. https://bunpro.jp/vocabs/hokkaido-island
  2. https://bunpro.jp/vocabs/åŒ—ęµ·é“-Hokkaido-%28island

Well, okay, for some reason, the first link stopped working, but I swear it was working a few minutes ago. :thinking: Maybe by the time you read this it’ll start working again?

There are a couple issues with this situation.

Issue #1

First off, I need to mention that when I was accessing it via the first link, the ā€œCopy a link to this page to the clipboardā€ button would always copy the first link. But when I was accessing it via the second link, the Copy Link button would copy the second link!

Thus, according to the Copy Link button, there are two ā€˜canonical’ links to the same Vocab page.

So, first issue is that the Copy Link button (ā€œCopy a link to this page to the clipboardā€) should always have the same, single, canonical URL in it. Probably this should come directly from the DB, perhaps with a dedicated ā€˜canonical URL’ field for each vocab – not copy it from the browser (which is how I’m presuming it’s currently being done).

Note that this issue (#1) is about the Copy Link button. The bigger issue (#3) will be about the underlying page/data structure, although the two issues are fairly linked.

Issue #2

Second, and this is a relatively minor one, but I just want to get it out of the way: The second link contains an open-parenthesis ā€˜(’, but this messes up the Hyperlink feature of these here forums, so that you can’t easily copy/paste the URL into a forum post. I had to manually insert a URL-encoded %28 in order to get the second link to show up without issue. Otherwise, it ends up like this:

Which leads to a 404.

So, second issue is that canonical URLs should (ideally) not contain characters that mess up the BP forum’s Hyperlinking feature(s). (Or maybe somehow fix the forums so that they can handle the pasting of URLs with such characters.)

Issue #3

Fundamentally, though, the main issue is that item pages (Vocab or Grammar) should have a single, unique, canonical URL associated with them (again, related to issue #1, but this time about the data rather than the UI).

It should be the same canonical URL regardless of the URL used by the browser (or whatever other inclusion mechanism) to access it. Think of it like a ā€˜permalink’, although perhaps in the back-ground it might be modifiable, unlike a true permalink – but modifying it should be rare and done carefully.

There are numerous possible issues that could come up as a result of allowing different canonical-seeming URLs to bring up the same canonical page. In fact, I’m having a brain fart right now and having a hard time coming up with some of them, although I had a few in mind when I first started writing this out. :sweat_smile:

A basic example, though:

User editing the same page via different URLs, but not realizing they represent the same page, may be making edits on each copy, in different browser tabs. May save edits on one tab, then switch to second tab, save those edits, effectively over-writing the edits made in the first tab.

I use a Duplicate Tabs plugin to prevent myself from doing this kind of thing, but it is defeated if the same page can be opened using two different URLs.


In general, while it’s generally okay for different URLs to lead to a single canonical page, the page itself should have a unique ā€˜identity’, accessible in the form of a single canonical URL. For much the same reasons it’s best to have a single canonical ID for database records. Especially when linking things. You’re basically ā€˜asking for trouble’ by not having them.

Anyway, kinda fizzled out there due to brain fart. But I think the fact that the Copy Link button produces different URLs depending on how the page is accessed is alarming enough, IMHO. Anywho… yeah.
:sweat_smile:

1 Like