- Issue created by @ambient.impact
-
Ambient.Impact →
committed 0240d78b on 2.x
Issue #3391460: refreshless.js: Use core 10.1 httpMethod for AJAX: See...
-
Ambient.Impact →
committed 0240d78b on 2.x
-
Ambient.Impact →
committed 1a298486 on 2.x
Issue #3391460: RefreshlessPageState: InputBag::get() comment edit:...
-
Ambient.Impact →
committed 1a298486 on 2.x
-
Ambient.Impact →
committed b931d683 on 2.x
Issue #3391460: RefreshlessPageState: revert back to GET whoops: $...
-
Ambient.Impact →
committed b931d683 on 2.x
-
Ambient.Impact →
committed 571e3da8 on 2.x
Issue #3391460: refreshless.js: Ajax success now use Promises: See core...
-
Ambient.Impact →
committed 571e3da8 on 2.x
- Issue was unassigned.
- Status changed to Fixed
about 1 year ago 8:32pm 7 October 2023 - 🇨🇦Canada ambient.impact Toronto
Alright, so I think I've fixed the blockers to this working and have it running again.
There's still a difficult to pin down bug that sometimes causes an exception in the JavaScript on popping state by hitting back when it tries to construct a
State
object but passesnull
as thehistoryPosition
parameter due to an incorrectsessionStorage
ID. Given that it only sometimes happens and we're planning on replacing the homegrown JavaScript with Hotwire Turbo which is expected to handle this for us, I'm not going to try and fix it but rather focus on the port instead. -
Ambient.Impact →
committed 571e3da8 on 8.x-1.x
Issue #3391460: refreshless.js: Ajax success now use Promises: See core...
-
Ambient.Impact →
committed 571e3da8 on 8.x-1.x
-
Ambient.Impact →
committed 0240d78b on 8.x-1.x
Issue #3391460: refreshless.js: Use core 10.1 httpMethod for AJAX: See...
-
Ambient.Impact →
committed 0240d78b on 8.x-1.x
-
Ambient.Impact →
committed 1a298486 on 8.x-1.x
Issue #3391460: RefreshlessPageState: InputBag::get() comment edit:...
-
Ambient.Impact →
committed 1a298486 on 8.x-1.x
-
Ambient.Impact →
committed b931d683 on 8.x-1.x
Issue #3391460: RefreshlessPageState: revert back to GET whoops: $...
-
Ambient.Impact →
committed b931d683 on 8.x-1.x
Automatically closed - issue fixed for 2 weeks with no activity.