You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replicating the process of generating the chat demo, there are a number of points I have picked up; if deemed necessary, I am willing to break these up into individual ones.
1 - un-reproducible behaviour. The elimination of the previously submitted string in the new message form remains in the refreshed form. form:
This default state for referrer is actually unaccepted by Chromium. origin-when-cross-origin is what google digests. The google default to a very restrictive position. Feature policies and Content-Security policies come to mind, given that hotwire is dealing with frames. Is this not a potential for breakage? what guidelines should be followed?
3 - Some older browsers (I recognize and accept my quirkiness), take a pass on hotwire - Safari 9, but also Safari 11 which isn't exactly cro-magnon...
Do we have an idea of which standards are baseline in order to inform/handle such uses?
4 - premisse: Firefox is my go-to browser and gets used heavily. In my observation, javascripts generate unexpected behaviours relating to the DOM.
This is an example. Aside form a page refresh, is there a way to 'reboot' the DOM if one notices the browser acting flaky (again this may be a moot point given the premisse) ?
The text was updated successfully, but these errors were encountered:
I'm having the same issues. I did noticed that they have since updated the new form (source), but I still can't get it to work as expected (neither can any of my co-workers).
abaldwin88
added a commit
to abaldwin88/hotwire-rails-demo-chat
that referenced
this issue
Jun 4, 2022
Upgrade to Rails 7 with `rails new` default project scaffolding
Fixeshotwired#11 Content Policy prevented stimulus controller from loading which caused chat input to not clear on submit
abaldwin88
added a commit
to abaldwin88/hotwire-rails-demo-chat
that referenced
this issue
Jun 4, 2022
Upgrade to Rails 7 with `rails new` default project scaffolding
Fixeshotwired#11 Content Policy prevented stimulus controller from loading which caused message input to not clear on submit
Replicating the process of generating the chat demo, there are a number of points I have picked up; if deemed necessary, I am willing to break these up into individual ones.
1 - un-reproducible behaviour. The elimination of the previously submitted string in the new message form remains in the refreshed form. form:
stimulus controller
It even stays put as other messages are being driven to the room
Something might be wrong with the stimulus set-up, something missing, but where/how to de-bug?
2 - Feature policies. Rails's guide defines a default state.
This default state for referrer is actually unaccepted by Chromium.
origin-when-cross-origin
is what google digests. The google default to a very restrictive position. Feature policies and Content-Security policies come to mind, given that hotwire is dealing with frames. Is this not a potential for breakage? what guidelines should be followed?3 - Some older browsers (I recognize and accept my quirkiness), take a pass on hotwire - Safari 9, but also Safari 11 which isn't exactly cro-magnon...
Do we have an idea of which standards are baseline in order to inform/handle such uses?
4 - premisse: Firefox is my go-to browser and gets used heavily. In my observation, javascripts generate unexpected behaviours relating to the DOM.
This is an example. Aside form a page refresh, is there a way to 'reboot' the DOM if one notices the browser acting flaky (again this may be a moot point given the premisse) ?
The text was updated successfully, but these errors were encountered: