Free soloed some large rocks in #IndianCove@JoshuaTreeNPS 10 days ago. Look out @AlexHonnold! 😂 📷 @nancyyeh #wallclimbwednesday #joshuatree #climb #boulder #optoutside #getoutside
While on a long weekend #yogaretreat in Joshua Tree, a few of us ventured out during our mid-day breaks to Joshua Tree National Park. I found nice solid granite rocks to climb, and on Sunday several with just enough grips for hands and (just barely) my Nike Pegasus shoes (wishing I’d thought to bring my #Evolv approach shoes or #FiveTen Dragons). Still made it to the top, then took over twice as long to downclimb. Grateful for many years of bouldering practice.
Last Saturday’s #run: 20.5 miles & 3570' under, through, and above the clouds. Started with #SFRC, chose a different route, to Cardiac Hill and back. My farthest #trailrun yet.
1 Looking back down Fox 2 Just before, Fox trail up into the clouds 3 Black beetle, saw it moving, paused for the up close shot 4 Coastal trail down to Muir Beach 5 Mist shrouded switchbacks I had just ascended 6 Milk thistle flower 7 Cardiac Hill view towards a cloud covered Pacific ocean 8 Snack time, my first @GUEnergyLabs #Stroopwafel 9 Happy to have made it halfway 10 Back down to Heather Cutoff switchbacks
The W3C Advisory Board keeps track of some issues in a private repository in the W3C GitHub org: https://github.com/w3c/AB/issues and in my opinion the AB should move to tracking issues publicly by default instead.
This requires two things: 1. creating new AB issues in a public forum/repo by default, and 2. analyzing current open issues to see if they can be moved to being public issues.
I have created the public label in the existing repo to help with the latter, and am attempting to label this issue accordingly as well.
As background, I created the public W3C AB wiki page five years ago which has served the group and W3C community quite well in practice. I think the AB can similarly benefit from public issues discussion by default.
Saturday’s #longrun: 16.5 miles & 2300'+ started with ~12 miles from home to the Tennessee Valley Trailhead, joined friends for a bit more, nearly 14 to the #beach. Climbed up for a view, ran back to the parking lot.
1. View of the city from SCA trail 2. Sunrise on the Panhandle park 3. Crissy Field Marsh 4. Golden Gate and Bridge 5. Flowers on the run up to GGB 6. Rolling hills and the Pacific 7. Alta trail and forest 8. Tennessee Beach 9. 📷 @thats_a_moret #selfie with Kelsey 10. View from Coastal Fire Road
And I started at the end of the last corral for the #SFM first half marathon (photo 3), due to a series of transport mishaps! Race day bus route changes, cabs ignoring all attempts to hail (losing all sympathy for ride-hail ires).
After a longer than expected warm-up (2.4 miles!), I finally caught a bus on Market street to the Embarcadero. The last corral for the SFM First half marathon was lining up to start. Took a quick pitstop and walked to the back of the corral.
Got a good start and set a decent pace up to Aquatic Park and around to the Marina. I walked a bit every couple of miles. Ignoring my pace, I ran with my breath.
After running by the bridge (under the roadway), down Lincoln to Seacliff, the race directed us on to 26th avenue into the park. Everything felt familiar from my practice run last Sunday, but a bit faster, despite the humidity.
This new course (without the bridge) felt harder (more vertical climb I’m pretty sure).
I didn’t see a single November Project person in the course or race. In fact I didn’t see anyone I knew at all. Quite a contrast from last year’s full marathon.
I finished, just grateful to do so, feeling strong, without injury. That’s 13 half marathons. After walk-jogging home, I stretched, cleaned up, and met November Project friends for brunch in Potrero flats, where they had cheered and handed out water at mile 23 of the full marathon.
Twin Peaks #hillsforbreakfast in #clouds (1), #sunshine in Glen Canyon (2-3), succulents en route back to Twin Peaks (4), #extravert up Tank Hill (5), Mount Olympus (6), Corona Heights (7-8), Buena Vista (9-10) for 8.9 miles & 2533'
Mozilla invites you to a complementary (and complimentary) all day Decentralized Web Hackers Day and IndieWebCamp SF at our Mozilla San Francisco offices.
Spend a day creating the web you want collaborating with others doing the same, using the latest in decentralized and indieweb technologies.
Schedule
10:00 Opening keynotes and lightning intros/demos
11:15 BarCamp breakout session scheduling
12:00 Open hack day and discussion sessions
16:00 Lightning Demos!
17:00 Wrap-up and transit to DWeb pre-party
We will open the day with a few brief introductory keynotes to set the stage and get your creativity flowing, followed by a round of lightning intros/demos by participants who want to (yes that means you!)
In our usual BarCamp style, we’ll spend a few minutes having participants propose different discussion/hacking sessions for the day and pick rooms & time slots. Sessions will start promptly after scheduling. Don’t worry if this is your first time participating in a BarCamp, we will explain the process for everyone and especially make sure newcomers get a chance to propose their session ideas.
Final sessions and hacking will wrap at 16:00 and we will all reconvene in the main room for a round of lightning demos of hacks, insights, whatever you made or thought up.
Afterwards we’ll direct you to local transit that will take you to the Internet Archive for the Decentralized Web Summit Science Faire and Pre-party (requires separate registration)
Is this the same problem? I thought perhaps with the switch from GraphQL to the GitHub v3 API a few weeks (months?) ago, this might have been fixed at the same time.
Whatever the cause is, some labels are still not getting through via publish.
#TBT to the Rodeo Valley 30k and how good the first half felt, running uphill (1) and downhill (2). Then learning in the second half that I had what it took to endure hours of 90-95°F temperatures to run, jog, and hike to finish a five hour trail race. Race photos 📷 Chris Cleary @insidetrail
Once CSS Scrollbars has been resolved and published as a FPWD,
the scrollbar-gutter property should be moved from CSS Overflow 4 to CSS Scrollbars.
This was discussed briefly at the recent f2f in Sydney with general agreement
among those discussing that scrollbar-* properties ought to be in the same spec,
and @astearns pointed out to me the detail
that it would be better to move it after FPWD,
since 'scrollbar-gutter' has already been published in a FPWD, and I agree.
1 panoramic from Horizonal Control Mark Coyote Ridge 2 2 look back down Miwok 3 view of Pirates Cove from Coastal Trail 4 Pirates Cove beach 5 Pirates Cove looking North 6 Stepping into the coarse sandy surf at Tennessee Beach 7 Tennessee Beach looking North 8 vertical panoramic of sun and mottled clouds over the beach 9 large whale bone 10 remaining whale bones and beach looking South
First long run since my 30k. Quite a sluggish start, took me a few miles to warm-up and get into a good groove. Subsequent hills felt easier than when I ran them two weeks ago. Another bright sunny day with temperatures mostly in the 80s F, much better than the 90s during the 30k!
There appears to be consensus at least in the current comments on this issue for adding a property to modify scrollbar size, with some additional preference for that to be treated as a maximum size, allowing implementations to show smaller scrollbars if it’s more appropriate.
I have captured the use-cases mentioned here and to me in person on the wiki accordingly:
Regarding the concern about terminology raised by https://github.com/silverwind about using "width" for horizontal scrollbars, vs the suggested alternative "thickness", note that CSS already has a notion of modifying the width of horizontal and vertical "bars" in the 'border-width' and 'outline-width' properties.
In particular note the pre-existing 'border-top-width' and 'border-bottom-width' properties (https://drafts.csswg.org/css-backgrounds-3/#border-width) which specifically apply to horizontal borders. Thus I think it is both ok and desirable to use "width" to refer to the scrollbar size as well, since it is consistent with those existing properties, and matches what web developers will likely already be familiar with in CSS.
I’m going to specify a 'scrollbar-width' property that takes length units that sets the maximum width of any scrollbars on an element when they are shown. 'auto' will be used as the initial value that means just use the platform default scrollbar size.
t
