Skip to content

Stuff from here and there

Spider

I found a cool spider on my rose bush. @goodwitch knew what it was.

Previously unmentioned by me here at Web Teacher are two posts at BlogHer from the last couple of days. The first was Gmail’s New Priority Inbox. The second was Two Decades of Women, a personal essay that has nothing to do with tech, Internet, web education or teaching.

At eHow, these articles have been getting the traffic:

Useful links: interactive film, web educators, women in tech

The Wilderness Downtown is a fascinating interactive film built in HTML5 for Chrome by some Google folks. It only works in Chrome, but it’s worth downloading and installing Chrome if you don’t already have it, just to see what is possible with the technology. There are other Chrome experiments, also.

Dive into the Modern Web – a workshop for educators at Web Directions USA looks like a great event for web educators.

Want one more woman at tech conferences? Gotta love Dori’s sense of humor in making a serious point about one particularly qualified female geek.

A blog + a feed + a reader = a more efficient you

Pop quiz time. Do you read several blogs each day? If yes, do you navigate to each one separately? If yes, would you like to save time by subscribing to each one and reading it in a feed reader?

If you are not sure what a feed reader is, this article is for you. I use a feed reader, and I foolishly assumed most blog readers do, too. But recently I read a couple of books. One was Professional Blogging for Dummies. The other was Create Stunning HTML Email That Just Works. Both of these books mentioned statistics about the number of people who use feed readers (or RSS readers, as they are also called). The percentage was very low – 15 or 20%. The number shocked me a bit, because feed readers save a lot of time for people who like to read blogs.

Read the complete post at BlogHer to learn how to use the Google Reader and subscribe to blog feeds.

Useful links: IT Consulting, big web shows, tech in education

Where are the women in IT Consulting by Chip Camden is from Tech Republic.

Maybe you saw this weekend’s rant over at TechCrunch saying that it’s not men’s fault that we can’t find any women in tech. My response is to offer some kudos to Jeffrey Zeldman and Dan Benjamin at The Big Web Show, where there doesn’t seem to be any problem finding both interesting men and women to talk tech with.

5 Ways Tech Startups Can Disrupt the Education System is must reading for any educator.

Useful Links: Video, movies, blogging tax

Good news for HTML5 Video is about H.264.

Movies. Now YouTube is offering instant movie downloads, and there’s an app for watching movies from Netflix on your phone.

5 Myths About Philadelphia’s ‘Blogging Tax’. The Philadelphia tax came up in a discussion in the comments on this post, so I thought it bore mention here.

Resolving conflicts in CSS made simple

Two or more conflicting CSS rules are sometimes applied to the same element. What are the rules in CSS that resolve the question of which style rule will actually be used when a page is rendered by a browser? The answer is, “it’s complicated.” Several factors are involved. I’ll give you a brief explanation of each factor.

Inheritance

Some properties are passed from parent to child. For example, this rule in a style sheet would be inherited by all child elements of the body and make every font on the page display as Georgia.

body {font-family: Georgia;}

The Cascade

Within the cascade, more than one factor can figure into determining which one of several conflicting CSS rules will actually be applied. These factors are source order, specificity and importance. Location is part of the cascade, too.

Source order means the order in which rules appear in the style sheet. A rule that appears later in the source order will generally overrule an earlier rule. Consider this example.

body {font-family: Georgia;}
h1, h2, h3 {font-family: Arial;}

Because the h1, h2, and h3 selectors are in the source order after the body rule, the headings would display in Arial, not in Georgia.

Specificity

Specificity is determined by a mathematical formula, but common sense can help you understand it.

p {font-family: Georgia;}
.feature  p {font-family: Arial;}

In this case, the selector .feature p is more specific than the selector p. For any paragraph assigned to the class ‘feature’ the font-family would be Arial. Common sense tells you that selecting a paragraph that belongs to a particular class is a more specific choice than selecting all paragraphs. The more specific selector overrules the less specific selector.

!important

There are rules that are declared !important. !important rules always overrule other rules, no matter what inheritance, source order or specificity might otherwise do. A user created stylesheet can use !important to overrule the author’s CSS.

*{font-family: Arial !important;}

This rule would mean that everything (* selects everything) would be Arial no matter what other rules were used in the CSS.

Location

Style rules can exist in a number of locations in relation to the HTML page affected. The location of a rule also plays into determining which rule actually ends up being implemented. The locations are:

  1. Browser style rules
  2. External style rules
  3. Internal style (in the document head) rules
  4. Inline style rules
  5. Individual user style rules

In the list, the browser style rules are the most “distant” from the HTML page, the individual user styles are the “closest.” Within this cascade of style declarations, the closest rule wins. An inline style overrules an external style, which overrules a browser style.

Related posts:

Is there a gender issue with Facebook Places?

Facebook Places

I’ll do anything for BlogHer. Even try out Facebook Places. I resisted Foursquare and Gowalla and other similar services. But when BlogHer asked me to report on Facebook Places, I couldn’t say no.

First, I’ll explain how to use it. Then I’ll describe how reactions to it have split along gender lines. Finally, I’ll tell you how to deal with privacy settings for this new Facebook service.

Read the full article at BlogHer.

Useful Links: HTML5 + RDFa, data visualization

HTML5 + RDFa = time to get rid of that 20th Century furniture is an interesting high level look at web interactions and a lot of specific hits on HTML5, RDFa, Drupal and SPARQL. Plus, just looking at this blog makes me feel good. Love the primary colors. It cheers me up almost as much as seeing a Miró.

The beauty of data visualization is David McCandless at a TED Talk. (Hat tip to DigitalDiva for pointing to it.) It’s worth your time to watch.

Dear Adobe, Can Dreamweaver do this?

What do you wish Dreamweaver would do? I’ll bet you have a pet peeve or a longed-for feature.

I’d like to see Dreamweaver do some new things. Or maybe, do some old things differently.

  1. I’d like to see proper icons in the Property Inspector for bold, italic, strong, and em. Bold and italic may make a comeback in HTML5, which is going to be even more confusing to users who don’t know all the facts about semantic markup. And while they’re at it, could they add a button for cite?
  2. I’d like to see a pull down list of ARIA roles that could be applied to elements. Maybe in the Property Inspector or maybe in a menu under Accessibility.
  3. If a user changes the ID of a form field with the Property Inspector, I’d like to see the “for” attribute for the label change to match.
  4. I wish there was a way to add scope=col or scope=row to table header (th) cells through the WYSIWYG menus. Why couldn’t it be added to the Header section of the Table Dialog? A checkbox labeled “Include scope attribute” would do the trick.
    Dreamweaver Table Dialog Window

Useful Links: 28 HTML5 Features, Longdesc, Gender & Usability, Net Neutrality

28 HTML5 Features, Tips, and Techniques you Must Know is an excellent list from Jeffrey Way.

Longdesc may be dropped from the HTML5 spec. Right now it’s in the “let’s argue about it” phase. WebAxe has a discussion by podcast with some folks who examine the issue. The Fate of Longdesc in HTML5.

What’s the fate of the “longdesc” attribute in HTML5? Can or should the “aria-labelledby” ARIA attribute replace it? These are some of the controversial issues discussed by Dennis and guests John Foliot (@johnfoliot), Everett Zufelt (@ezufelt), and Joe Dolson (@joedolson).

Gender Differences in Web Usability. I was fine with this report, until I got to the part about the woman wanting a pink tab.

ReadWriteWeb has a good infographic about net neutrality.