Last modified: 2007-06-08 01:10:46 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 5498 - Provide page cache timestamp as JavaScript variable
Provide page cache timestamp as JavaScript variable
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-07 20:25 UTC by lɛʁi לערי ריינהארט
Modified: 2007-06-08 01:10 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description lɛʁi לערי ריינהארט 2006-04-07 20:25:42 UTC
Hallo!

It might be a good ides to expand the "final comment" before </body></html>
with additional information:
revisionid; it should be available in the browsers sorce code anyway
timestamp; I suppose the timestamp when this page gets generated / cached
???

I assume this would facilitate referencing and fault finding.

best regards reinhardt [[user:gangleri]]
Comment 1 Brion Vibber 2006-04-08 01:04:54 UTC
It would be far more useful to provide that in 
machine-readable form for JS usage.
Comment 2 lɛʁi לערי ריינהארט 2006-04-08 06:44:26 UTC
(In reply to comment #1)
> It would be far more useful to provide that in 
> machine-readable form for JS usage.

Agree. Start with the machine-readable form for JS usage. If it is to cryptic
(if people could not associate it with its meaning) then please append a comment
character and a minimal legible hint.
Comment 3 lɛʁi לערי ריינהארט 2006-04-08 20:21:23 UTC
I wonder how action=purge effects should be included.

*scenario*
User A describes the rendering of page X with revision_id N at (UTC) time NOW.
Templates might change, software updates might be involved, action=purge migth
generate different code.

If user B looks at page X with revision_id N at (UTC) time LATER he should be
able to see at least the timestamp of last *rebuild* of the page. This timestamp
may differ from the timestamp of the last change for page X.
Comment 4 Brion Vibber 2006-04-08 20:58:17 UTC
Please stop posting random junk all over bug reports. Thanks.
Comment 5 Rob Church 2007-03-29 21:39:27 UTC
The revision identifier is exposed as wgCurRevisionId. I'm not sure we need the
"page touched" timestamp...
Comment 6 Rob Church 2007-06-08 01:10:46 UTC
Original issue was fixed, the page_touched value would be of limited use to client-side scripts.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links