-
Notifications
You must be signed in to change notification settings - Fork 270
Using browser's back button #35
Comments
@yigitbacakoglu Thanks for the bug report. If anyone can fix this issue, please submit a PR 👍 |
will work on this ... |
@kenny-hibino issue is caused by Turbolinks not playing nice with JS. Removing turbolinks should fix this R |
@rawdreeg fork it and fix it i will give you a vps to work in i love this project but i dont know anything about ruby i want to use it as and open source project team blog |
@rawdreeg @kenny-hibino : This issue has been already reported to react-rails. Please see this github issue. and changed has been pushed into master branch of |
gread news :D
…On 13 March 2017 at 14:17, AjayBarot ***@***.***> wrote:
@rawdreeg <https://github.com/rawdreeg> @kenny-hibino
<https://github.com/kenny-hibino> : This issue has been already reported
to react-rails. Please see this github issue
<reactjs/react-rails#159>. and changed has been
pushed into master branch of react-rails. So by updating react-rails gem
this issue will resolved. And I prefer not to remove turbolinks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEA5c9kCuQdxDNx_6g5e-VDq--xzuREPks5rlTPugaJpZM4KpTCg>
.
|
@AjayBarot I merged your pull request! I'm still seeing the bug with the back navigation. Do you have bandwidth to investigate further? |
@kenny-hibino : I suspect progress bar issue and some part of UI is not showing after back button. Issue is with
I am working on solution 1 and I will submit PR tomorrow. Please share your suggestion and concern. |
@AjayBarot is there any news? |
@strivemag : I created one pull request regarding this issue. and pull request still need to reviewed. #45 |
If you click 'Back Button' on browser or (swipe your magic mouse to left) after you click any link that changes the view (eg. Click on a tag), latest view slides down and the container remains empty.
The text was updated successfully, but these errors were encountered: