Yes, I can.
1 Like
Is this a known error? Happens during standard reviews, as well as reviewing new items (which completely crashes the session and forces me to restart). Using Firefox.
edit: s̶e̶e̶m̶s̶ ̶t̶o̶ ̶e̶x̶c̶l̶u̶s̶i̶v̶e̶l̶y̶ ̶h̶a̶p̶p̶e̶n̶ ̶a̶f̶t̶e̶r̶ e̶n̶t̶e̶r̶i̶n̶g̶ ̶a̶n̶ ̶i̶n̶c̶o̶r̶r̶e̶c̶t̶ ̶a̶n̶s̶w̶e̶r̶ ̶a̶n̶d̶ t̶r̶y̶i̶n̶g̶ ̶t̶o̶ ̶m̶o̶v̶e̶ ̶o̶n̶t̶o̶ ̶t̶h̶e̶ ̶n̶e̶x̶t̶ ̶i̶t̶e̶m̶.̶
1 Like
I might have spoken out in haste, and this morning I am paying very careful attention to exactly when this situation arises.
This morning, I have grammar question where everything depends on where the input focus is:
- I can not pinch to zoom out if the Google keyboard is up and the focus is in the answer input box.
- If I move the focus out of the answer input box, by manually clicking outside of it, then the Google keyboard naturally disappears, and I can manually pinch to zoom out
- As soon as I move the focus back into the answer input box to bring up the keyboard, the page automatically zooms in and I’m back in state 1.
The zoom problem always affects the following grammar questions, independent of whether I have typed anything:
- “The C1 is impassable over a range of 5 kilometers due to snow. Please use the detour.”
- Just because I said those things to him, he got extremely depressed."
This grammar question changes zoom behavior depending on the focus and the length of my answer:
- "Since I was 30 minutes late, I cannot afford to keep my customers waiting anymore. "
When I start entering my answer, everything is fine. Once my answer reaches 6 hiragana characters, the page re-renders and I enter state 1 above. If I delete the 6th hiragana character, I can again zoom out the page as normal.
To test the hypothesis that this might be related to the length of the Japanese text in the sample sentence, I experiment with:
- “Judging from the fact that she speaks English fluently, she probably lived abroad when she was young.”
This question doesn’t show any zoom problems until I enter the 8th hiragana character. At that point, the Japanese sentence text (which of course also includes my answer), stops being rendered in two lines of text and is rendered on 3 lines. At that point, the zoom problem appears and I enter state 1 described above.
After seeing this, I tested in multiple sentences and confirmed that I had the zoom problem if and only if the Japanese example sentence with my answer were long enough to be rendered on 3 lines on the screen.
I hope this helps.
1 Like
Hi, I’ve been really enjoying the app, thanks for all the hard work! I noticed that the styling on the API page (Log in - Japanese Grammar Explained | Bunpro) doesn’t appear to be getting applied:
Looking at the browser console it looks like it’s trying to load SCSS files, there might be a build step missing?
1 Like
Thanks for the fantastic app!
I’m starting to use Self-Study sentences more and it looks like editing answers in existing sentences doesn’t work at the moment. Whenever I try to type anything in the input - it rolls back immediately to what it was.
More of a question than bug report, but is it possible to use kanji in the answer? I really like how BunPro substitutes the kana for kanji once I enter my answer. For me, it 'd be useful for 頃 grammar point since I’m not that used to seeing the kanji in the wild yet.
Thanks!
1 Like
Hey! Are you able to update Firefox and try again?
Looking into this bug now!
Thanks for the report.
As opposed to Kanji in the answer, this may be something we add support for in the future.
1 Like
Thanks for all the details! Very thorough.
- When you open the Google Keyboard, do you visibly notice the screen zoom in?
- Also, do you have your font size setting set to 12px?
I’ll do some more investigation!
Yes, the screen visibly zooms in when I open the keyboard.
No, my font size preferences are set to 16px. Should’ve mentioned earlier. At 12px, I do not see any problems with unexpected zoom in until the Japanese sentence (w. my answer included) hits 6 lines.
I am usually on the other side of this type of back and forth for reproduction, so I appreciate you not giving up on me!
1 Like
@Jake
the shift enter can create the next line but it could not enter to the next paragraph to have the next point form like when enter could do previously. What the keyboard shortcut for the next paragraph?
1 Like
IPadOS 17.0 (beta 2)
Bunpro app (beta 0.4.1)
The bar at the top that shows our progress was full but I still had reviews to do 
(19/23)
Under path of Tobira chapter 1 始めるis missing.
I can replicate this bug.
Will take a look and see why!
EDIT: Will be fixed in the next update
1 Like
All good info!
Gonna attempt a fix. Will tag you in the update post once it’s done.
Please also make sure your Firefox is on the latest version
1 Like
When singlely adding items from the deck list, the added items default to “cloze” instead of the decks selected style.
Deck is set to manual input style. When I chose “Add to Reviews” from deck list the items are added but the items are added as “close” which is not the selected preference to this deck.
Context this is N4 deck vocab page 8
Noticed that the “New Grammar Per Day” chart (which sometimes doesn’t load until refreshing) has an extra blank month on the end, August 2023 in this case:
I seem to be getting a comment about having “missed 13 boxes” a lot, though 13 doesn’t seem to correspond to anything in my reviews.
Perhaps it’s a joke that I just don’t get? 
The number of missed items was 1 here, but still “missed 13 boxes”:
1 Like
If I had to guess that would be a Crash Bandicoot joke.
The ending screen of a level will give a very similar message
3 Likes
It’s a Crash Bandicoot joke but I should probably actually wire it up so the exact number of missed items shows
2 Likes
Hihi super weird: in the Android app (v0.4.1+91), I just finished JLPT N3 (yay!), but when I set my target to N2 and clicked the Learn New Batch button, I got a congratulations for finishing N2 screen telling me to set my target to N1! …which I did for kicks, but then it said I’d finished N1 already as well? It looks like it works on the website (still via phone browser), though, so it’s not a total blocker – I can learn new grammar points that way, just not with the app