Skins

[Ryan Wilson]

If the changes don't compromise the overall aesthetic of Dusk, I'm thinking
about keeping them in. However, if a specific Sandstone pieces make it an
eyesore, I'd overwrite on Dusk with Classic styles. Basically, I'm trying
to keep size down and the .gitignore file untouched, if possible.
On Tue, Feb 2, 2016 at 2:38 PM Dylan Hardison <dylan at mozilla.com> wrote:

> On Tue, Feb 2, 2016 at 3:19 PM, Ryan Wilson <theycallmefish at gmail.com>
> wrote:
> > I've started the process of converting Sandstone to replace Classic, but
> I
> > wanted to pose a question before I got too far into the process:
> >
> > Since Dusk will remain as a built-in custom option, are we okay if Dusk
> > inherits some of the style design of Sandstone? If not, Dusk will become
> > much larger, as it will need to inherit most of the CSS from Classic.
>
> You can do what you think is best to make Sandstone the default and
> base. If Dusk has to change for this, go ahead and do it.
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=theycallmefish@gmail.com>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20160202/8a24fec0/attachment.html>