Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug report] Pickadate not loaded when using kiosk with chromium #252

Open
r-xyz opened this issue Sep 7, 2024 · 3 comments
Open

[Bug report] Pickadate not loaded when using kiosk with chromium #252

r-xyz opened this issue Sep 7, 2024 · 3 comments

Comments

@r-xyz
Copy link
Contributor

r-xyz commented Sep 7, 2024

The date and time picker (when creating reservations in kiosks) are not working anymore in recent versions of chromium.

Steps to reproduce

  1. Open kiosk page using Chromium
  2. Select a tool, make new reservation
  3. Click on date/time fields: nothing happens

Notes

This seem to only affect datetime pickers; Keyboard and numeric input keypad work as expected in kiosks.
Everything works correctly in Firefox, but a similar warning is shown in console, too (see below).

Logs

Chromium console logs

[Violation] Permissions policy violation: Synchronous requests are disabled by permissions policy. [3 times]
  send @ jquery.min.32015dd42e95.js:4
  ajax @ jquery.min.32015dd42e95.js:4
  n._evalUrl @ jquery.min.32015dd42e95.js:4
  domManip @ jquery.min.32015dd42e95.js:3
  append @ jquery.min.32015dd42e95.js:3
  (anonymous) @ jquery.min.32015dd42e95.js:3
  n.access @ jquery.min.32015dd42e95.js:2
  html @ jquery.min.32015dd42e95.js:3
  load_complete @ Cleanroom/:166
  j @ jquery.min.32015dd42e95.js:2
  fireWith @ jquery.min.32015dd42e95.js:2
  x @ jquery.min.32015dd42e95.js:4
  (anonymous) @ jquery.min.32015dd42e95.js:4
  load
  send @ jquery.min.32015dd42e95.js:4
  ajax @ jquery.min.32015dd42e95.js:4
  ajax_message @ nemo.b6574a18bcce.js:503
  ajax_post @ nemo.b6574a18bcce.js:492
  tool_report_problem @ Cleanroom/:243
  onclick @ Cleanroom/:1

Uncaught TypeError: $(...).pickadate is not a function
    at eval (eval at globalEval (jquery.min.32015dd42e95.js:2:2538), <anonymous>:5:50)
    at eval (<anonymous>)
    at Function.globalEval (jquery.min.32015dd42e95.js:2:2538)
    at n.domManip (jquery.min.32015dd42e95.js:3:17203)
    at n.append (jquery.min.32015dd42e95.js:3:14886)
    at n.<anonymous> (jquery.min.32015dd42e95.js:3:16246)
    at n.access (jquery.min.32015dd42e95.js:2:30124)
    at n.html (jquery.min.32015dd42e95.js:3:15917)
    at Object.load_complete (Cleanroom/:166:32)
    at j (jquery.min.32015dd42e95.js:2:26911)
  eval @ VM223:5
  globalEval @ jquery.min.32015dd42e95.js:2
  domManip @ jquery.min.32015dd42e95.js:3
  append @ jquery.min.32015dd42e95.js:3
  (anonymous) @ jquery.min.32015dd42e95.js:3
  n.access @ jquery.min.32015dd42e95.js:2
  html @ jquery.min.32015dd42e95.js:3
  load_complete @ Cleanroom/:166
  j @ jquery.min.32015dd42e95.js:2
  fireWith @ jquery.min.32015dd42e95.js:2
  x @ jquery.min.32015dd42e95.js:4
  (anonymous) @ jquery.min.32015dd42e95.js:4
  load
  send @ jquery.min.32015dd42e95.js:4 
  ajax @ jquery.min.32015dd42e95.js:4
  ajax_message @ nemo.b6574a18bcce.js:503
  ajax_post @ nemo.b6574a18bcce.js:492
  tool_report_problem @ Cleanroom/:243
  onclick @ Cleanroom/:1

Chromium issue log:

Deprecated feature used:
  Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
Affected resources:
  jquery.min.32015dd42e95.js:4

Firefox Console log:

Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help https://xhr.spec.whatwg.org/#sync-warning                     [jquery.min.32015dd42e95.js:4:14161](http://localhost:8000/static/jquery.min.32015dd42e95.js)
@r-xyz
Copy link
Contributor Author

r-xyz commented Sep 9, 2024

@r-xyz
Copy link
Contributor Author

r-xyz commented Nov 12, 2024

Hi @rptmat57,
I am somehow unable to reproduce anymore on 6.1.0.dev.
Is it possible it was fixed in dev? I had a look at the commits history, but I could not find anything directly related.

@rptmat57
Copy link
Contributor

Hi, I don't remember working on this.
It's possible that chromium reverted their previous change to make this a blocking error rather than a simple warning

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants