Is it possible, now we have DOM, to get the IDs of all form elements
on a page and get/set thir contents?
I'm thinking of from frontend code here, so a form or password manager
could potentially be written (I'm not thinking of writing one, just
whether I can put things in place so an external one is possible).
This patch is intended to support the parsing and storage of the "writing-mode" property, which is one of the building blocks for vertical text in css (support for which is currently required by the HTML5 track element and obviously is a pretty important localization feature -- and just simply looks cool, too).
The layout side of things can be dealt with elsewhere, but first and foremost is getting libcss to support the property.
A link to the current draft is here http://dev.w3.org/csswg/css-writing-modes/ with the writing-mode property in particular described in http://dev.w3.org/csswg/css-writing-modes/#writing-mode
It is quite likely that there are things substantially wrong, including the lack of test data (I haven't figured out how to get the test suite to even build and run yet, `make test` seems to fail substantially here.)
So some review would be good, I'd like to get this approved by netsurf devs before trying to squeeze it into mozilla-servo.
Any and all feedback is much appreciated, thanks a bunch.
On Tue, 28 May 2013 19:52:13 +0100, Vincent Sanders wrote:
> This means that user options files will now only contain the options
> which differ from the defaults. This will alow us to alter the
> defaults in future and have everyones choices actually update instead
> of being overidden by old saved default values that might not be useful.
Is there any way to modify the defaults outside of nsoption_init?
I have to open a screen before I can set some of the values, but I
can't open the screen until options are initialised (as the parameters
are in there). So I'd like to set some defaults at a later time which
then get applied, unless of course the user has already set their own