The initial example as written seems quite forced - in part because it shows some static HTML code, and then relies on an assumption that it was dynamically generated by script.
Changing it for an event that was added to a calendar using <input type="datetime-local"> from HTML 5.2 might be clearer - and draw attention to a built-in and shipping feature that generates floating time zone information.
source [en]
The initial example as written seems quite forced - in part because it shows some static HTML code, and then relies on an assumption that it was dynamically generated by script.
Changing it for an event that was added to a calendar using
<input type="datetime-local">
from HTML 5.2 might be clearer - and draw attention to a built-in and shipping feature that generates floating time zone information.