Clockpicker displays and hides immediately after updating Chrome version to 73 on materializecss

Related searches

I have timepicker/clockpicker which is configured like this by materializecss (v0.100.2).

<label for="time">Time</label>
<input id="time" type="text" class="timepicker">

$('.timepicker').pickatime({
   default: 'now'
});

When we click on the text field the clockpicker modal opens, but immediately it gets closed. https://codepen.io/anon/pen/evQxPy

This happens after I have updated my chrome version to 73

I had the same problem and solved like this way:

 $('.timepicker').on('mousedown',function(event){
event.preventDefault();})

Hope this will work it is working perfectly for me

Clock displays and hides immediately after updating Chrome , Clock displays and hides immediately after updating Chrome version to Pickadate not working with materialize 0.100.2 with the latest chrome TimePicker clockpicker popup closes immediately after open (on chrome v73)� Download ZIP CSS < 6KB, JS < 9KB, after minified. Browser support. All major browsers are supported, including IE 9+. It should look and behave well enough in IE 8. Device support. Both desktop and mobile device are supported. It also works great in touch screen device. Dependencies. ClockPicker was designed for Bootstrap in the beginning.

Not sure, if this is a bulletproof solution but this works for me especially with clockpicker. The version should be materializecss (v0.100.2). In materialize.js file, Line No: 8913

ClockPicker.prototype.show = function (e) {

Just wrap setTimeout( 200 ms) inside this whole function, works well.

Chrome Update 73, Chrome Update 73 - Materialize CSS JS trigger error, After the latest Chrome Update 73, if this is a bulletproof solution but this works for me especially with clockpicker. Clock displays and hides immediately after updating Chrome , @ Marzon We use all the time everywhere after updating from version 72 to version 73. Clockpicker displays and hides immediately after updating Chrome version to 73 on materializecss. This happens after I have updated my chrome version to 73.

@Subash Hi there.

ClockPicker.prototype.show = function (e) {

Just wrap setTimeout( 200 ms) inside this whole function, works well.

For me it works only if I use arrow function cause then I keep "this" from previous context or you have to pass it through setTimeout.

Materialized dropdown and datepicker issues on new chrome version, Clockpicker displays and hides immediately after updating Chrome 问题: I have timepicker/clockpicker which is configured like this by materializecss (v0. 100.2). This happens after I have updated my chrome version to 73� The navbar is fully contained by an HTML5 Nav tag. Inside a recommended container div, there are 2 main parts of the navbar. A logo or brand link, and the navigations links.

Date/Time Picker in materializecss bug on Chrome/Chromium 73 , It is happening all the time everywhere after updating from version 72 to version 73. If set, updates the display's logical bounds origin along the y-axis. See documentation for boundsOriginX parameter. DisplayMode (optional) displayMode: Since Chrome 52. If set, updates the display mode to the mode matching this value. If other parameters are invalid, this will not be applied.

Date picker popup appears and immediately disappears when you let go of a zip file containing the unminified version materialize.js file that I updated and a I didn't correctly wrap the timeout around the clockpicker in #11. google chrome opens up but does not display on screen Hello, very recently google chrome has this issue in which it opens up but it does not show on my screen. If i go to the task bar and glide over google chrome it shows its open and it loaded just fine but it does not show up on my screen.

ClockPicker was designed for Bootstrap in the beginning. So Bootstrap (and jQuery) is the only dependency(s). Since it only used .popover and some of .btn styles of Bootstrap, I picked these styles to build a jQuery plugin.

Comments
  • Possible duplicate of Chrome Update 73 - Materialize CSS JS trigger error
  • This is a regression in Chrome 73. We have released pickadate 3.6.1 which should resolve this. See bugs.chromium.org/p/chromium/issues/detail?id=941910 for the regression in Chrome.
  • @DanielRuf we use only materialize.js not pickadate.js. So how do we fix it on materialize.js? Thanks
  • materialize uses a customized version of pickadate. See github.com/amsul/pickadate.js/pull/1140/files for the needed changes.
  • But increase the timeout to 100.
  • Workes like a charm!