Closed bnjns closed 4 years ago
In GitLab by @bnjns on Apr 30, 2019, 23:01
Interesting, seeing as they both use the same rendering engine and the site was built in Chrome
In GitLab by @jordanlkirk99 on Apr 30, 2019, 23:10
I don't think stable Edge has quite switched over to Chromium yet.
In GitLab by @jordanlkirk99 on Apr 30, 2019, 23:11
changed the description
In GitLab by @bnjns on May 1, 2019, 21:47
@jordanlkirk99 Who wants to take it? Might be as simple as tweaking some CSS widths, but might be a problem with the display mode being used - possibly want to switch to using flexbox.
In GitLab by @jordanlkirk99 on May 2, 2019, 00:25
I'm afraid I tried playing with the widths and determined I don't know what I'm doing :p
In GitLab by @jordanlkirk99 on May 2, 2019, 18:52
assigned to @jordanlkirk99
In GitLab by @jordanlkirk99 on May 2, 2019, 18:53
mentioned in merge request laravel-site!97
In GitLab by @jordanlkirk99 on May 2, 2019, 18:53
created merge request laravel-site!97 to address this issue
In GitLab by @jordanlkirk99 on May 2, 2019, 18:58
Nvm I was stupid, a simple fix
In GitLab by @bnjns on May 31, 2019, 19:01
mentioned in merge request laravel-site!102
In GitLab by @bnjns on May 31, 2019, 19:03
closed via merge request laravel-site!102
In GitLab by @jordanlkirk99 on Apr 30, 2019, 21:24
Summary:
In Chrome the month of event times is offset the equivalent of a line below the day/time/name.
Actual behaviour (as seen in Chrome):
Expected behaviour (as seen in Edge + IE):
Steps to reproduce:
Look at the event times for any event in Chrome.
\label ~Bug