I would like to see options in the preferences of Safari, NetNewsWire and other WebKit apps for the following: • Defining your own Accept* HTTP headers. Please just give me a set of text fields so I can write my own headers! Especially Accept- Language, that's the most important—my system language is set to British English, yet Safari sends out requests with "en-us". :-/ • Ability to set 1pt to 1/72 inches, and read the screen DPI for digital devices. Unless the screen can report it's own DPI, whis will probably require a large lookup table with Apple and other manufacturers' displays enumerated. (FontBook has something similar for converting copyright strings into publishers' names). This would be a preference in the apps that use WebKit, and you can default to off if you want, but I need the sanity of a HTML client that will display a 10cm line at 10cm on screen, in print, in braille, on a TV, on a phone, wherever. Is there anyone else that would welcome these abilities? - Nicholas.
Nicholas,
• Defining your own Accept* HTTP headers. Please just give me a set of text fields so I can write my own headers! Especially Accept- Language, that's the most important—my system language is set to British English, yet Safari sends out requests with "en-us". :-/
If Safari sends out an accept header that is inconsistent with your system language setting, that seems like a plain old bug, and not something requiring a new feature to work around. It would be helpful if you filed the bug @ bugzilla.opendarwin.org, along with steps to reproduce it, and a comparison to other browsers' behavior. Geoff
On Jun 8, 2006, at 4:35 AM, Nicholas Shanks wrote:
I would like to see options in the preferences of Safari, NetNewsWire and other WebKit apps for the following:
• Defining your own Accept* HTTP headers. Please just give me a set of text fields so I can write my own headers! Especially Accept- Language, that's the most important—my system language is set to British English, yet Safari sends out requests with "en-us". :-/
Aside from the general feature you propose, your specific example sounds like a bug. I'd encourage you to report it at bugzilla.opendarwin.org, since a fix would benefit 1000x the people who would know how to customize their HTTP headers.
• Ability to set 1pt to 1/72 inches, and read the screen DPI for digital devices. Unless the screen can report it's own DPI, whis will probably require a large lookup table with Apple and other manufacturers' displays enumerated. (FontBook has something similar for converting copyright strings into publishers' names). This would be a preference in the apps that use WebKit, and you can default to off if you want, but I need the sanity of a HTML client that will display a 10cm line at 10cm on screen, in print, in braille, on a TV, on a phone, wherever.
I think it's a worthy problem, but when Apple tackles it (and it must be coming up, as monitors keep developing), I hope they do it at a system level instead of just in WebKit. It's an unappealing prospect to me to wind up with an effective zoom factor for web content, but not PDF and text content in all the non-WebKit apps I use. trey
Is there anyone else that would welcome these abilities?
- Nicholas._______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
On Jun 8, 2006, at 6:35 AM, Nicholas Shanks wrote:
• Defining your own Accept* HTTP headers. Please just give me a set of text fields so I can write my own headers! Especially Accept- Language, that's the most important—my system language is set to British English, yet Safari sends out requests with "en-us". :-/
In addition to filing a Bugzilla bug report, I would recommend filing a "Radar" bug report on http://bugreport.apple.com/. The reason for filing a second bug here is that it will be added to Apple's internal bug database, so if the bug isn't in WebKit code, then Apple will have a way to track the bug internally. Note that you must create a 100% free "online" Apple Developer Connection account before you can file a bug on this site. If you do file a Radar bug, please report the Radar bug number on Bugzilla, and vice-versa.
• Ability to set 1pt to 1/72 inches, and read the screen DPI for digital devices. Unless the screen can report it's own DPI, whis will probably require a large lookup table with Apple and other manufacturers' displays enumerated. (FontBook has something similar for converting copyright strings into publishers' names). This would be a preference in the apps that use WebKit, and you can default to off if you want, but I need the sanity of a HTML client that will display a 10cm line at 10cm on screen, in print, in braille, on a TV, on a phone, wherever.
You may also be interested in these WebKit blog entries by Dave Hyatt: High DPI Web Sites http://webkit.opendarwin.org/blog/?p=55 High DPI (Part 2) http://webkit.opendarwin.org/blog/?p=56 CSS Units http://webkit.opendarwin.org/blog/?p=57 Dave
participants (4)
-
David D. Kilzer
-
Geoffrey Garen
-
Nicholas Shanks
-
Trey Matteson