Chromium does not honor DOM Javascript variable document.lastModified

Bug #1604161 reported by Tommy Pollák
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

It seems that the Chromium web browser Version 51.0.2704.79 Ubuntu 16.04 sets the JavaScript variable document.lastModified to the current date and time if the document is browsed with the file protocol, e.g. file:///media/OS/Users....

Firefox shows 2016-07-18 17:36:12 for my document whereas Chromium for the same document now shows 2016-07-18 17:46:36, a time that changes every time the page is loaded.

Exactly the same JavaScript function works perfectly well for Chromium when provided by HTTP, see http://www.osttimorkommitten.se/.

Tags: xenial
affects: ubuntu → chromium-browser (Ubuntu)
tags: added: xenial
Revision history for this message
Nathan Teodosio (nteodosio) wrote :

1. Opened a local file in Chromium 107.0.5304.62 , file:///home/nteodosio/a.html.
2. Opened the Chromium console with Ctrl+Shift+i.
3. Entered document.lastModified and verified that the output was both correct and did not change with time.

Changed in chromium-browser (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.