Last modified: 2007-06-04 19:35:41 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 10107 - Autothumbnail size
Autothumbnail size
Status: RESOLVED DUPLICATE of bug 495
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-06-02 12:14 UTC by Nicholas
Modified: 2007-06-04 19:35 UTC (History)
0 users

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


Attachments

Description Nicholas 2007-06-02 12:14:29 UTC
The current auto thumbnail feature automatically defaults to 180px. This appears too small on larger resolutions. I suggest that the auto thumbnail be dependent on the user's resolution.

800x600 = 180px
1024x768 = 220px 
and so on.

This would be useful to anon users who are unfamiliar with setting their image preferences.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-06-03 01:59:55 UTC
This is only potentially possible when browsers consistently implement reasonable client-side scaling.  Since scaling is presently server-side so thumbs don't look like garbage, we can't know what resolution the user is using.  And then there's the issue of caching.
Comment 2 Nicholas 2007-06-03 10:24:51 UTC
Forgive me for asking what may be a stupid question: But when a user logs into the site won't the header information grab the user's browser resolution and mediawiki automatically serve up the appropriate image resolution if not already specified? 


(In reply to comment #1)
> This is only potentially possible when browsers consistently implement
> reasonable client-side scaling.  Since scaling is presently server-side so
> thumbs don't look like garbage, we can't know what resolution the user is
> using.  And then there's the issue of caching.
> 
Comment 3 Raimond Spekking 2007-06-03 13:34:22 UTC

*** This bug has been marked as a duplicate of bug 495 ***
Comment 4 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-06-03 19:28:12 UTC
(In reply to comment #2)
> Forgive me for asking what may be a stupid question: But when a user logs into
> the site won't the header information grab the user's browser resolution and
> mediawiki automatically serve up the appropriate image resolution if not
> already specified? 

I'm not clear on what you're asking, but any attempt to serve different images to different anons based on screen resolution will lead to large-scale cache fragmentation, which is not acceptable for performance reasons.  Perhaps that answers your question.
Comment 5 Brion Vibber 2007-06-04 19:35:41 UTC
HTTP header information does not include screen size.

It's possible for *client-side* JavaScript to request screen size from the browser, but:
a) that runs on the client, hence after you have sent content
b) that only runs if JavaScript is enabled
c) the browser may or may not return a value
d) screen size, geometry, and resolution can vary quite a bit
e) users' preferences can vary even more

While it would be possible to rig up something that made images bigger for people with big screens, it would likely be more effort than it's worth and make more people annoyed than it would make happy.

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


Navigation
Links