fix: some ui issue

[devchenyan]

issues:

• Some UI issues to fix or adjust later Magickbase/neuron-public-issues#302
• Issue on UI withdrawing from NervosDao #2954

Screen-2023-12-14-192327.mp4

Screen-2023-11-26-150409.mp4

[devchenyan]

/package
Packaging for test is done in 7095467778. @devchenyan

[FrederLu]

/package Packaging for test is done in 7095467778. @devchenyan

There is still a time inconsistency problem on Linux.

[devchenyan]

When the user's device time is non-East 8 time, the display of the release time may not match the one in the details.

So after communicating with @FrederLu , we consider labelling the release time as East 8 time in the release information. cc @Keith-CY

[Keith-CY]

When the user's device time is non-East 8 time, the display of the release time may not match the one in the details.

So after communicating with @FrederLu , we consider labelling the release time as East 8 time in the release information. cc @Keith-CY

The datetime set in the release note is UTC+0, so it can be formatted with the timezone

[devchenyan]

When the user's device time is non-East 8 time, the display of the release time may not match the one in the details.
So after communicating with @FrederLu , we consider labelling the release time as East 8 time in the release information. cc @Keith-CY

The datetime set in the release note is UTC+0, so it can be formatted with the timezone

The datetime in releaseNotes is formatted with UTC+8 and can't be formatted with the timezone.

[Keith-CY]

When the user's device time is non-East 8 time, the display of the release time may not match the one in the details.
So after communicating with @FrederLu , we consider labelling the release time as East 8 time in the release information. cc @Keith-CY

The datetime set in the release note is UTC+0, so it can be formatted with the timezone

The datetime in releaseNotes is formatted with UTC+8 and can't be formatted with the timezone.

My bad, I mean the published_at field of https://api.github.com/repos/nervosnetwork/neuron/releases/tags/v0.111.0 can be formatted with UTC+0, and it's expected to be the same date in the release note.

The date in the release note is updated manually and prone to be wrong, e.g. the release date was updated with an incorrect time but not found in code review(https://github.com/nervosnetwork/neuron/pull/2973/files), but published_at is set by program and more reliable.

[devchenyan]

When the user's device time is non-East 8 time, the display of the release time may not match the one in the details.
So after communicating with @FrederLu , we consider labelling the release time as East 8 time in the release information. cc @Keith-CY

The datetime set in the release note is UTC+0, so it can be formatted with the timezone

The datetime in releaseNotes is formatted with UTC+8 and can't be formatted with the timezone.

My bad, I mean the published_at field of https://api.github.com/repos/nervosnetwork/neuron/releases/tags/v0.111.0 can be formatted with UTC+0, and it's expected to be the same date in the release note.

The date in the release note is updated manually and prone to be wrong, e.g. the release date was updated with an incorrect time but not found in code review(https://github.com/nervosnetwork/neuron/pull/2973/files), but published_at is set by program and more reliable.

To avoid misunderstanding, we can mark the release time as East 8 district time .eg: 0.112.0 (2023-12-07 UTC+8)

[Keith-CY]

When the user's device time is non-East 8 time, the display of the release time may not match the one in the details.
So after communicating with @FrederLu , we consider labelling the release time as East 8 time in the release information. cc @Keith-CY

The datetime set in the release note is UTC+0, so it can be formatted with the timezone

The datetime in releaseNotes is formatted with UTC+8 and can't be formatted with the timezone.

My bad, I mean the published_at field of api.github.com/repos/nervosnetwork/neuron/releases/tags/v0.111.0 can be formatted with UTC+0, and it's expected to be the same date in the release note.
The date in the release note is updated manually and prone to be wrong, e.g. the release date was updated with an incorrect time but not found in code review(#2973 (files)), but published_at is set by program and more reliable.

To avoid misunderstanding, we can mark the release time as East 8 district time .eg: 0.112.0 (2023-12-07 UTC+8)

Indeed, I will append the timezone in following release notes

[devchenyan]

/package
Packaging for test is done in 7203849589. @devchenyan