Today, around the world, people are joining Web inventor Tim Berners-Lee in wishing the World Wide Web a happy 25th birthday. To mark the occasion, everyone is encouraged to share birthday greetings on social media using #web25. Select greetings will also be posted on a virtual birthday card on the official anniversary site webat25.org.

“The Web’s billions of users are what have made it great,” said Berners-Lee. “I hope that many of them will join me today in celebrating this important milestone. I also hope this anniversary will spark a global conversation about our need to defend principles that have made the Web successful, and to unlock the Web’s untapped potential. I believe we can build a Web that truly is for everyone: one that is accessible to all, from any device, and one that empowers all of us to achieve our dignity, rights and potential as humans.”

Read the full press release, welcome message and video from Tim Berners-Lee, and special greetings to the Web.

Please visit the Web’s 25th anniversary site regularly for more details on activities and events all year long, including W3C’s 20th Anniversary Symposium which will take place in Santa Clara, California, and will be live-streamed.

Here in the Office of Alumni Relations, we spend a lot of time telling stories about and talking with our wonderfully supportive alums. However, we’ve decided to turn the tables and take time to get to know the people behind the scenes — the  advancement and alumni relations staff members who are hard at work on behalf of our alumni. Today we’ll be hearing from Stanyell Bruce, the Director of Alumni Relations.

Name: Stanyell Bruce
Job Title:  Director of Alumni Relations
Focus Area: I oversee the day-to-day operations of the alumni relations office and, along with my team, come up with various ways to engage and connect with UMBC’s over 62,000 amazing alumni.
Years at UMBC: 7.5 years

Q: Where are you from originally?

A: Bronx, NY

Q: What do you love most about UMBC?

A: I love the UMBC story (the little engine that could except on a much grander scale).

Q: What’s your favorite thing about your job?

A: I love meeting alumni and hearing their stories. Depending on when an alum attended UMBC, they have a totally different experience or lens that they look through; no matter the experience, alums are proud to be part of the UMBC story. As a relationship builder and connector, I feel like the work I do has real meaning and will make an impact for years to come.

Q: What do you like most about yourself?

A: That I can adapt to pretty much any situation. Of course there have been a few times when I was like a deer in headlights, but overall I like the fact that I adapt pretty easily.

Q: If you could be another staff member for a day, who would it be and why?

A: Jim Lord! I would love to know what it feels like to be a design director and 1 – have such creative genes and 2 – get to see my work (and the work of my team) all over this campus.

Q: What is one word you would use to describe your job?

A: Challenging!

It’s Tuesday which means that the Treehouse Show is back! In episode 81 of The Treehouse Show, Nick and Jason (@jseifer) talk about user experience patterns, Angular JS, lazily loading ads, and more. There’s also the usual round up of horrible jokes and bad puns. Ahoy!

This Week’s Links

• jimbojsb/launchrocket

• raphaelcruzeiro/jquery-notebook

• Tether – Marrying elements for life

• Outdated UX patterns and alternatives

• How to Learn AngularJS – Your AngularJS Sherpa | ng-newsletter

• Why you should move that button 3px to the left | Google Ventures

• madgex/lazy-ads

• CSS Shake

The post Outdated UX Patterns, Learning Angular JS, Lazy Loading Ads | The Treehouse Show Episode 81 appeared first on Treehouse Blog.

Tomorrow marks the third annual Scholarship Luncheon celebrating donors and their contribution to support our UMBC students. This yearly meet-and-greet event is a great opportunity for donors to get to know the scholarship recipients and understand just how big an impact their gifts have on the UMBC students and community.

A highlight of the event is the opportunity to hear from two special speakers: a donor and a student. This year, donor Ken Pittman ’80, Economics, of PNC Wealth Management will share the story of why he supports UMBC and one of the Linehan Art scholars will share the story of how receiving a scholarship has changed her life and advanced her studies.

More than just a time to express gratitude, however, the scholarship luncheon promotes the possibility of future philanthropy – the students are able to see the faces behind the scholarships and realize that the people giving these gifts are real people with passions just like themselves with a desire to give back to others and their community. It’s heartwarming for the donors to meet the students face to face and students are also touched at the chance to learn the story behind the scholarship.

And even as the luncheon ends and our donors and students go their separate ways, the effects of their meeting often last beyond this day, beyond UMBC and even extend into the personal lives of the donors and recipients. One particular student was so grateful to his donor that he made the effort to follow up and maintain a relationship. Equally, the donors enjoy the chance to see where the students are after graduation: where they are working, what has happened in their lives and what they are working toward in their future.

As we at UMBC see it, this is what philanthropy should be: a lasting legacy and the chance to make new connections. We appreciate all the donors who support our students – you are making a very real mark on our campus and changing lives.

Make your mark today! Support students scholarships.

The following is a guest post by Agop Shirinian. Agop ran into an interesting scenario where he needed an element to be scrollable in one direction, while allowing the overflow in the other direction. You'd think that's what overflow-x and overflow-y are for, but it's not that simple. I'll let Agop explain.

So you're tasked with creating a scrollable menu with submenus that pop out when you hover over a parent menu item.

Simple!

Create a list for the menu, add some nested lists for the submenus, position the nested lists based on their parent list items, voilà!

See the Pen Scrollable menu with pop out submenus (broken) by Agop (@agop) on CodePen.

Wait, that's not right. Oh, of course, we used overflow: auto - perhaps if we use overflow-x: visible, the horizontal overflow of the submenus will be visible:

See the Pen Scrollable menu with pop out submenus (broken #2) by Agop (@agop) on CodePen.

What gives? Why do we still get scrollbars?

The Problem

If we look at the W3C spec, we find the following explanation:

The computed values of ‘overflow-x’ and ‘overflow-y’ are the same as their specified values, except that some combinations with ‘visible’ are not possible: if one is specified as ‘visible’ and the other is ‘scroll’ or ‘auto’, then ‘visible’ is set to ‘auto’.

Basically, this:

overflow-x: visible;
    overflow-y: auto;

Turns into this:

overflow-x: auto;
    overflow-y: auto;

So we can't have visible horizontal overflow if the vertical overflow is invisible, and vice versa.

And if we can't have visible horizontal overflow, we can't have our pop out submenus!

The Solution

Interestingly enough, if we omit the position: relative from the menu items, the submenus do show up, positioned based on their closest positioned ancestor. In this case, they don't have a positioned ancestor, so they're positioned relative to <body>:

See the Pen Scrollable menu with pop out submenus (step 1) by Agop (@agop) on CodePen.

Basically, in order for an absolutely positioned element to appear outside of an element with overflow: hidden, its closest positioned ancestor must also be an ancestor of the element with overflow: hidden.

Knowing this, we can add a wrapper around the menus to act as the closest positioned ancestor for each submenu. Then, whenever the user hovers over a menu item, we can position the submenu wrappers using a bit of JavaScript:

See the Pen Scrollable menu with pop out submenus by Agop (@agop) on CodePen.

And that's it! Since neither the menus nor the menu items are positioned, the submenus are able to pop out of the hidden/scrollable overflow. Now we can have as many levels of nested submenus as we want, and we won't get any undesired clipping.

Takeaway

Unfortunately, this method of showing items that would otherwise be hidden is very obscure.

It'd be nice if we could specify a clip depth, which would control which ancestor in the hiearchy would be responsible for clipping a particular element:

./* Fair warning: not real code */
    .submenu {
      /* only an ancestor 2 levels up can clip this element */ 
      clip-depth: 2;
    }

Or, even better, perhaps we could specify the clipping parent by a CSS selector:

/* Fair warning: not real code */
    .submenu {
      /* only an ancestor that matches the .panel selector can clip this element */
      clip-parent: .panel;
    }

Popping Out of Hidden Overflow is a post from CSS-Tricks