search

DOMjudge / domjudge

DOMjudge programming contest jury system
https://www.domjudge.org
GNU General Public License v2.0
720 stars 254 forks source link

Time format not accepted #234

Closed Abdelghafour01 closed 8 years ago

Abdelghafour01 commented 8 years ago

The default time format is not accepted while creating a new contest: image

eldering commented 8 years ago

Hi, I cannot reproduce this. Which version of DOMjudge and which O/S and browser+version are you using? Can you try in one or two other browsers?

corneym commented 8 years ago

I too have been seeing this on Domjudge/5.1.1 using Chrome 53.0.2785.116. The behaviour does not repeat in Firefox 47.0.1 or on Internet Explorer 11.0.9600.18449

From: Jaap Eldering [mailto:notifications@github.com] Sent: Saturday, 24 September 2016 2:42 AM To: DOMjudge/domjudge Subject: Re: [DOMjudge/domjudge] Time format not accepted (#234)

Hi, I cannot reproduce this. Which version of DOMjudge and which O/S and browser+version are you using? Can you try in one or two other browsers?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/DOMjudge/domjudge/issues/234#issuecomment-249242165 , or mute the thread https://github.com/notifications/unsubscribe-auth/AClEDK7RP72g5IwGe0zrMeTFnINGNe9hks5qtAFUgaJpZM4KFKSK . https://github.com/notifications/beacon/AClEDEDj-aaYIY6A0YxJoPWqaivJ8puKks5qtAFUgaJpZM4KFKSK.gif

eldering commented 8 years ago

Ok, I think I fixed this Chrome specific issue (I could reproduce it with Chromium on Debian Jessie). Please see the fix in the referenced commits.

sokol-kosta commented 7 years ago

Thanks for pointing this out. It was driving me crazy. I am using DOMjudge 5.1.1 on Mac OS X with Google Chrome 53.0.2785.116. I have always used Google Chrome to create the contests without any problem. Only recently, when I tried to update one of the contests to postpone its end time the error appeared. I confirm that using Safari everything went smooth.

I haven't pulled the fix for Chrome yet but thanks for fixing it.