aboutsummaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)Author
2011-11-30prepare dillo-3.0.2release-3_0_2corvid
2011-11-30freshmeat changed its name to freecode in Octobercorvid
2011-11-29documenting non-dillo codecorvid
2011-11-17never treat URI schemes case-sensitivelycorvid
2011-11-12some isascii()corvid
2011-11-11continuedcorvid
2011-11-11fix IPv6 addr recognitioncorvid
I was under the impression that the brackets were part of the host syntax, but a_Url_hostname() shows that they are part of the _authority_ and are stripped out when making the hostname.
2011-11-11dns: hostname comparisons not case-sensitivecorvid
2011-11-11generic font-family names not case-sensitivecorvid
2011-11-11locale-independent ASCII character case handlingcorvid
Basically, I and i are different letters in Turkic languages, and this causes problems for str(n)casecmp and toupper/tolower in these locales when dillo is dealing with ASCII.
2011-11-08mergeJorge Arellano Cid
2011-11-08Allow "view source" to reload upon user requestJorge Arellano Cid
2011-11-08image magic is case-sensitivecorvid
2011-10-30Bind Ctrl-{PageUp,PageDown} to tab-{previous,next}.Jeremy Henty
2011-10-23back out c6cbf3ae7ffd (LC_CTYPE)corvid
I'd asked furaisanjin about input methods, and it sounded like it would be okay, but it turns out that something goes wrong on his system after all (LANG and the various LC_* set to ja_JP.eucJP normally, "while converting to Kanji, font width is half and it's not easy to recognize.") So I can't get away with the lazy fix after all.
2011-10-22middle click on stylesheet menu item opens in new tab/windowcorvid
copied from history callback, of course
2011-10-22text-transform propertycorvid
2011-10-22reset LC_CTYPE to C (for the benefit of Turkic locales)corvid
The standard solution to I and i being different letters in Turkic locales is to make your own ASCIIfied strcasecmp/toupper/tolower, but I'm not aware of us currently having any need/use for non-C LC_CTYPE.
2011-10-20add a text input when input type is not recognizedcorvid
bug #1018 submitter requested behaviour a little more friendly to html5, which sounds sensible as bits of that infinite monstrosity start showing up more often...
2011-10-17typocorvid
2011-10-17don't reset table cells to white-space: normal when no nowrap attributecorvid
the value of the property is inherited, and might not be 'normal'
2011-10-14font-size property, let absolute-size and relative-size values have larger ↵corvid
effect Using roughly 1.2 per step, a value mentioned in the CSS2.1 spec. Firefox appears to use a value that is similar but a little larger. http://css-tricks.com/2580-css-font-size/ says that "keyword sizing is pretty consistent across browsers and platforms", and perhaps someday we'll want to go out of our way to make them exactly the same, but this is a start.
2011-10-11digest auth: in Authorization header, some stupid software requires IE's ↵corvid
field ordering found by furaisanjin.
2011-10-11digest auth: in Authorization header, quote digest-uri-valuecorvid
found by furaisanjin. http://www.rfc-editor.org/errata_search.php?rfc=2617 has an entry showing that this should be done. Now, the RFC was done in 1999, and the error was reported in 2010 and verified in 2011, so we're lucky with our timing, but isn't it surprising how slow of a process it is to clean out the corners like this in important specifications?
2011-10-11digest auth: some software doesn't accept whitespace in "token = value"corvid
found by furaisanjin. My reading of rfc 261[67] is that this whitespace is fine. But easy enough to take out...
2011-10-06rework line breaking and fix white-space:nowrap handlingJohannes Hofmann
2011-10-01Minor changes in use-after-free patch to match the CCC handling styleJorge Arellano Cid
2011-09-29rest of digest authenticationJustus Winter, corvid
Justus contributed the original patch in April 2009. I read RFCs, fixed bugs, restructured, tested.
2011-09-29add digest filesJustus Winter, corvid
2011-09-29add md5 filesJustus Winter
2011-09-29rename variablecorvid
Use the name from rfc2616 to make it easier to understand
2011-09-25let the enter key trigger buttons when possiblecorvid
Topic brought up by Alexander recently. In FLTK2, Enter and Space would both trigger buttons. In 1.3, only Space does it. I asked the FLTK guys about this, and I learned that Space to trigger buttons is actually old-school X behaviour that I somehow never became aware of.
2011-09-25brace positioncorvid
2011-09-25use-after-freecorvid
I accidentally went to the url "80", got an unfamiliar error msg, and immediately wondered what valgrind would think of this unfamiliar path. And valgrind found a bug.
2011-09-24if not following a redirection, show body of redirecting pagecorvid
as suggested by Axel Beckert in http://lists.auriga.wearlab.de/pipermail/dillo-dev/2011-September/008992.html
2011-09-21prepare dillo-3.0.1release-3_0_1Johannes Hofmann
2011-09-19shorter cookies-not-sent MSGcorvid
2011-09-18rename fncorvid
Trying to make it a little clearer. It's surprising how there isn't a good, brief, clear term for this. Discussion of the concept tends to start using words like "administration" and "control".
2011-09-17add show_quit_dialog dillorc optionJohannes Hofmann
2011-09-17color pref error MSGcorvid
2011-09-16use x,y for tools popupcorvid
2011-09-16position history menu below buttoncorvid
2011-09-16a compromise on tab appearance for the momentcorvid
It looks like plastic just _insists_ on mixing lots and lots of grey in, so if you pick a color that you like in plain/gtk+, it gets seriously washed out in plastic. There is a problem of getting nearly indistinguishable colors.
2011-09-16FL_THIN_UP_BOX for tabscorvid
2011-09-16staticcorvid
2011-09-16update TLDscorvid
What an awful situation it is in general.
2011-09-16don't print ALLOW MSGs in Capi_filters_testcorvid
2011-09-16privacy: never accept cookies in responses to third-party requestscorvid
as mentioned in section 7.1 of RFC 6265
2011-09-16put public suffix comparison directly in url.ccorvid
2011-09-14privacy: never send cookies in third-party requestscorvid
as mentioned in section 7.1 of RFC 6265