[User Manager] I can not know the expiration date of a user set out above

jdillard

Ah, gracias. It looks like when you go to edit a user, it doesn't show the date that you previously set. It reverts back to showing mm/dd/yyyy.

To replicate create a new user and set an expiration date. Hit Save. Then edit the user and look at the expiration field.

heper

@jd your procedure works just fine for me, the date is there (running todays build)

jdik

@jdillard:

Ah, gracias. It looks like when you go to edit a user, it doesn't show the date that you previously set. It reverts back to showing mm/dd/yyyy.

To replicate create a new user and set an expiration date. Hit Save. Then edit the user and look at the expiration field.

I did what you told me, but the problem persists.

jdillard

@heper:

@jd your procedure works just fine for me, the date is there (running todays build)

hrm. This is a gif from 2.3.1-RELEASE using chrome: https://i.imgur.com/RHMSzxO.gifv

edit: Seems to be a browser issue with the date input field. I opened Firefox after making the gif and the field was blank. I typed 04/23/2017 into the field and hit save. Then hit edit and the date was there. If I check in Chrome after that it still shows mm/dd/yyyy.

Steve_B

I have changed the element type from "date" to "text". It seems that browsers don't really support the "date" type consistently yet.

heper

the horror of webbrowsers … i wonder why they bother to make html standards at all, seems the inconsistency is the same as a decade ago

divsys

….seems the inconsistency is the same as a decade ago

No, no, no, you just aren't seeing it clearly - the performance of the inconsistencies is so much better than 10 years ago ::)

Gertjan

Added to that:
In the beginning, we had that very motivated bunch of programmers living in Redmond writing an OS, a text editor etc.
They also wanted a web navigator : they gave us IE.

Today, two decades later, the dust around IE finally starts to settle.

Another company, with other new motivations (more like data mining at the user's device …) started to write a new navigator.
But WE, as users, we learned our lessons well during the last 20 years : STAY AWAY from new browsers ... or eat dust :)

jdik

@Steve_B:

I have changed the element type from "date" to "text". It seems that browsers don't really support the "date" type consistently yet.

I am still waiting for the solution, I have already upgraded to the latest version. :-[

jdillard

I didn't make it in the last release, it is (will be) in 2.3.2 though.