Age | Commit message (Collapse) | Author |
|
|
|
spotted-by: corvid
|
|
|
|
Properly separate common image handling functions in CSS relevant
attribute parsing (a_Html_image_attrs) and image creation
(a_Html_image_new()).
This should also bring the code back a bit to what we had before
8214199c2703.
|
|
The url field can be NULL for images that have display:none set, causing
a crash when checking "Load Images" later.
|
|
|
|
|
|
|
|
|
|
For a discussion of the problem see:
http://dbaron.org/mozilla/visited-privacy
|
|
|
|
When matching descendant selectors we need to test all
possibilities and not just the first one.
While at it refactor CssSelector::match ().
Testcase:
<html>
<head>
<style type=text/css> .a > .b .c { font-weight:bold }</style>
</head>
<body>
<div class=a>
<div class=b>
<div class=b>
<div class=c>should be bold</div>
</div>
</div>
</div>
</body>
</html>
Noticed-by: Sebastian Geerken <sgeerken@dillo.org>
|
|
|
|
|
|
By moving buildUserAgentStyle and buildUserStyle from css.cc to
styleengine.cc we can avoid the circular dependency between css.hh
and cssparser.hh.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
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.
|
|
copied from history callback, of course
|
|
|
|
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.
|
|
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...
|
|
|
|
the value of the property is inherited, and might not be 'normal'
|
|
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.
|
|
field ordering
found by furaisanjin.
|
|
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?
|
|
found by furaisanjin.
My reading of rfc 261[67] is that this whitespace is fine. But easy enough
to take out...
|
|
|
|
|
|
Justus contributed the original patch in April 2009.
I read RFCs, fixed bugs, restructured, tested.
|
|
|
|
|
|
Use the name from rfc2616 to make it easier to understand
|
|
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.
|
|
|