tantek.com

t

  1. Long black table in front of a white wall, with plates, silverware, and catered food serving dishes of flatbread, salad, and two kinds of dressing.Vegan catered food: chickpeas with colored chard and other vegetables in a large metal container, being heated electrically, on a black table, with a blue floor below.Cater vegan by default (per Guardian environment article^1). Defaults matter, and changing them works (changes behavior).

    Instead of making "vegan" or "vegetarian" a special meal option, flip it around, and cater vegan by default, with special meal options for dairy (milk/cream/cheese/yogurt), meat, or fish (as well as other needs / sensitivities).

    Mozilla Berlin catered lunches are fairly simple, and all but one of the "normal" dishes were vegan(1,2). There was both vegetarian (with cream) and vegan salad dressings on the side. Lastly a "special meal" container had fish. Putting non-vegan additions on the side is another good technique.

    Several years ago, @aaronpk and I decided we would cater vegetarian by default at IndieWebCamps we ran. He’s vegetarian, and I’m pescetarian so that worked for us. We of course ask participants to tell us if they have any additional special meals needs, turns out nearly none did / do. Changing defaults works. Most recently at IndieWeb Summit we did more than 50% vegan dishes (all vegetarian) with no complaints.

    We leave it up to each city’s IndieWebCamp organizers to decide for themselves (in a very distributed decision-making BarCamp way), however I think we’re going to make at least vegetarian a suggested default for new organizers, while going with a vegan default for IndieWeb Summits in Portland.

    I’ve also been (repeatedly) advocating internally at Mozilla for the company to switch to vegan catering by default for events, especially the ones where people have to sign-up with a form and indicate any dietary requirements. Hasn’t happened yet but I’m not giving up. I can say I’ve had more and more people say they think it’s a clever idea and they like it. Eventually I expect enough support that change will happen.

    I admit that seeing @osbridge (Open Source Bridge) provide vegan meals by default for years definitely inspired me. Seeing a large conference do it makes you realize how doable it is.

    Things like this are why personal, small group, and company choices around food, consumption, environmental impacts do make an impact. By setting a good (if bold) example, you normalize it, you remove fear, you make it that much less strange for the next person to choose to do so, for themselves, their group, or their company. Eventually maybe you help inspire a policy maker, or enough people to influence a policy maker, and can impact local city decisions, maybe state, and more.

    Systemic change is possible, and it’s possible to work in parallel at all levels.

    #vegan #vegetarian #caterVegan #veganByDefault #defaultsMatter #resetAllDefaults #optionalDairy #optionalMeat #optionalFish #environment #environmental #optimist #futureOptimism #noFilter

    ^1 https://www.theguardian.com/environment/2018/may/31/avoiding-meat-and-dairy-is-single-biggest-way-to-reduce-your-impact-on-earth — just going to keep linking this.

    on

  2. Thanks https://github.com/patrickhlauke for catching this, the suggestions, and especially the precise WCAG links, very much appreciated.

    I’ve lightly edited the suggestions and incorporated them into a pull request:

    https://github.com/w3c/csswg-drafts/pull/4694

    Patrick, could you review that pull request?

    Feel free to suggest additional edits if necessary.

    I will wait for your positive review before merging. Thanks!

    on

  3. Per co-editor Rossen’s (https://github.com/atanassov) scope clarification as noted in issue #4693 (https://github.com/w3c/csswg-drafts/issues/4693), I agree it makes more sense to distinctly separate styling of scrollbar controls (specified by CSS Scrollbars), and any layout impacts or scrollability effects which have interactions with the rest of overflow and belong there (specified in CSS Overflow).

    Thus I am retracting this issue and closing without any changes.

    on

  4. The CSS Scrollbars editor’s draft has an update to the Computed value for scrollbar-color of:
     
    specified keyword or two computed colors

    which reflects the above resolution as of 2018-10-23: https://github.com/w3c/csswg-drafts/issues/3237#issuecomment-432224775
     
    That just leaves adding it to the changes section.

    on

  5. Note that Rossen later followed-up in that same meeting to undo that resolution:

    https://www.w3.org/2020/01/23-css-irc#T12-29-54

    "RossenF2F: Re. merging, scrollbar-width/color just styles controls... scrollbar-gutter is more about the box model

    ... so let's not move everything to scrollbars yet until we know what will remain there"

    So for now, this no longer impacts CSS Scrollbars.

    on

  6. The CSS Scrollbars first public working draft (https://www.w3.org/TR/2018/WD-css-scrollbars-1-20180925/) was published, with as requested removal of “scrollbar‑3dlight‑color, scrollbar‑arrow‑color, scrollbar‑base‑color, scrollbar‑darkshadow‑color, scrollbar‑face‑color, scrollbar‑highlight‑color, scrollbar‑track‑color, scrollbar‑shadow‑color”.

    Rather than a new 'overflow-style' property, see the CSS Overflow Level 4 (https://drafts.csswg.org/css-overflow-4/) specification for how it handles the related use-cases. I believe all consensus use-cases requested in this issue have been addressed, and this issue can be closed without any further edits.

    on

  7. CSS Scrollbars should clarify scope for styling scrollbar controls, not layout or what is scrollable

    on

    The CSS Scrollbars scope section provides details of scope but lacks a good summary. Per co-editor Rossen’s point in the CSSWG meeting today that “scrollbar-width/color just styles controls”, the spec should summarize that explicitly. Note that from start, CSS Scrollbars has had a intended conservative compat scope, rather than being a dumping ground for new feature requests, whether related or not.

    This is an editorial change because it is summarizing the existing scope as long ago agreed by the working group. The goal is to help reduce the chance of future scope creep. Plan is to add a summary like this at the top of the scope section, based on @atanassov’s remark:

    “The CSS Scrollbars Module is specifically for styling scrollbar controls themselves, e.g. their color & width in Level 1, and not their layout nor whether any content is scrollable. All layout impacts and content scrollability are specified in the CSS Overflow Module.”

    Labels: css-scrollbars, css-scrollbars-1, Needs Edits

    on