Greetings.
On Sun, 11 Jan 2015 08:15:28 +0100 sta...@cs.tu-berlin.de wrote:
> * Christoph Lohmann 2015-01-07 21:46
> > cope with two goals:
> > 1.) Make userstyles.org usable for surf.
>
> [...]
>
> I can imagine to add 2-3 more styles to better adjust to some sites I
> regularly visit, but can't
* Christoph Lohmann 2015-01-07 21:46
> cope with two goals:
> 1.) Make userstyles.org usable for surf.
could you provide some examples of useful userstyles.org styles.
All I've seen on userstyles.org is either for sites I don't visit
regularly or is about setting a car (fire, skull) as background
Heyho,
Christoph Lohmann wrote:
> You are removing the possibility to enforce some userstyle on the com‐
> mandline, which I don’t like.
What would be the usecase? I doubt passing the whole list as args or a file
which then needs to be parsed first is useful. However I can imagine a flag to
ove
Greetings.
On Wed, 07 Jan 2015 21:38:09 +0100 Markus Teich
wrote:
> since the css domain selectors do not work in webkit, another approach needs
> to
> be taken to support custom css for specific sites. In config.h there is now a
> list of regexes and corresponding css filenames. When a page is
Nick wrote:
> Great, I'm glad to see this, thanks for it. The opera inspired browser hiro
> posted to the list reminded me of this functionality, actually, and it's a
> good step towards more general customisable settings per website (e.g.
> cookies, javascript), as Christoph suggested a while ago.
On Mon, 17 Nov 2014 17:07:43 +
Nick wrote:
> You're right, it's only useful for sites you visit often, so
> compiled in would be best.
I completely agree. This is in line with the motivation for config.h.
Even more importantly, surf doesn't take long to compile.
I see no reason for parsed c
Quoth Markus Teich:
> Nick wrote:
> > I have a slight preference for a separate configuration file that is read at
> > runtime, as I think that would be more usable.
>
> I have to disagree here. The default css should be sane enough to work with
> most
> of the pages. The custom sites need then o
Nick wrote:
> I have a slight preference for a separate configuration file that is read at
> runtime, as I think that would be more usable.
Heyho Nick,
I have to disagree here. The default css should be sane enough to work with most
of the pages. The custom sites need then only be used for regula
Quoth Nick:
> Quoth Markus Teich:
> > since the css domain selectors do not work in webkit, another approach
> > needs to
> > be taken to support custom css for specific sites. In config.h there is now
> > a
> > list of regexes and corresponding css filenames. When a page is loaded and
> > userst
Quoth Nick:
> I haven't read the code closely yet, but at least in design I think
> this should definitely be upstream.
I just read the code, and tested it, and it all looks good to me. I
don't like assigning variables when they're declared (as you do
once), but it isn't uncommon practise in s
Quoth Markus Teich:
> since the css domain selectors do not work in webkit, another approach needs
> to
> be taken to support custom css for specific sites. In config.h there is now a
> list of regexes and corresponding css filenames. When a page is loaded and
> userstyles are active, the first en
since the css domain selectors do not work in webkit, another approach needs to
be taken to support custom css for specific sites. In config.h there is now a
list of regexes and corresponding css filenames. When a page is loaded and
userstyles are active, the first entry that matches the uri is use
12 matches
Mail list logo
