via s3.amazonaws.com

via s3.amazonaws.com ...»See Ya

Reunion

This summary is not available. Please click here to view the post.

i figured i'd stop teasing everybody and upload What Gets Me Hot (uncensored, etc.)

 from the mysterious norwegian pevanel125 whose Traci Lords library is unsurpassed. 

i'd like to thank him again for including some of my What Gets Me Hot! mashes in his collection and for his inspiration and friend to precocity!

i like the soundtrack!

wgmh.mp4 Watch on Posterous

1. Traci Lords First Film What Gets Me Hot! (Audio) whatgetsmehot.posterous.comMay 10, 2011 - 3 min Traci Lords First Film What Gets Me Hot! what gets me hot opening dogmeat good.wmv.wmv Watch on Posterous ...

2. Dogmeat Dailymotion Skin=Cappuccino Jukebox ... whatgetsmehot.posterous.comNov 13, 2010 Dogmeat Dailymotion Jukebox Skin=Cappuccino See and download the full gallery on posterous mrjyn_dogmeat ...

3. NOW YOU CAN SAY, 'I Finally Figured out 'WHAT ... whatgetsmehot.posterous.comApr 7, 2010 NOW YOU CAN SAY, " I Finally Figured out 'WHAT GETS ME HOT!' " Traci Lords' First Role (First Scene) by ...

4. Facebook | Videos Posted by Fans of What Gets Me ... whatgetsmehot.posterous.comJan 26, 2011 Permalink | Leave a comment »

5. BLACKCURRANT BODICE whatgetsmehot.posterous.comJan 6, 2011 Cho cynophagie's YouTube Channel What Gets Me Hot dogmeat's FriendFeed mrjyn's Flickr What Gets Me Hot ...

6. The Cramps (Bryan Gregory): Loving God Through ... whatgetsmehot.posterous.comSep 21, 2010 - 3 min Blogs 2 new results for blogspot site: whatgetsmehot (video) whatgetsmehot site:animoto.com By limbsandthings ...

7. Google Alert - a blogurl:http://whatgetsmehot.blogspot ... whatgetsmehot.posterous.comJun 30, 2010 THE ULTIMATE ELVIS DIARY! | What Gets Me Hot By limbsandthings@gmail.com (What Gets Me Hot) 1957 THE ...

8. HALLOWEEN Facebook STORY is IMPOSSIBLE ... whatgetsmehot.posterous.comOct 28, 2011 - 5 min LEAVE his camp of hate" S [S] Orry to be born! --- READ shocking story of what they did! * Including FateBOOK ...

9. La Cicciolina Outfits and Jeff Koon Wedding whatgetsmehot.posterous.comAug 25, 2011 - 2 min Masturbation (cont.) Here péripatéticienne crépusculaires somnambulisme What Gets Me Hot Traci Lords Ilona ...

10. Desiree Cousteau Pizza Girls - 80s Female Mud-Wrestling whatgetsmehot.posterous.comJul 25, 2011 - 9 min pizza_girls.mp4 Watch on Posterous Permalink | Leave a comment » ...

Stay up to date on these results:

• Create an email alert for what gets me hot site:whatgetsmehot.posterous.com

i figured i'd stop teasing everybody and upload What Gets Me Hot (uncensored, etc.)  from the mysterious norwegian pevanel125 whose Traci Lords library is unsurpassed.  i'd like to thank him again for including some of my What Gets Me Hot! mashes in his collection and for his inspiration and friend ...»See Ya

HTML5 Parser-Based View Source Syntax Highlighting

A new implementation of the View Source HTML and XML syntax highlighting has landed in Firefox.

Why?

The reason there is a new implementation is that the old implemention was based on the old HTML parser that we want to get rid of. The old View Source implementation was standing in the way of the goal to remove the old parser. Also, the old parser did some incorrect highlighting. Most notably, it flagged the unnecessary-but-permitted slash as an error on void elements (e.g. <br/>) because all such slashes were bogus in non-X HTML prior to HTML5.

The reason why the new implementation uses the HTML5 parser instead of using something new and Orion-integrated in the dev tools is that the new implementation was written before there were publicized plans to integrate dev tools with View Source. Furthermore, there is no way to get HTML syntax highlighting right without the highlighter running the whole HTML(5) parsing algorithm, because tokenizer state transition decisions depend on the tree builder state.

New Features

The first and foremost feature is not user-visible per se. It is the non-use of the old parser code in order to be able to get rid of the old parser. However, using the old parser had user-visible consquences.

More Correct Highlighting

As already mentioned, the old parser unconditionally highlighted the slash in <foo/> as red regardless of the element name. Furthermore, the old parser failed to get the highlighting of tricky inline scripts right (when the inline script contained the string </script>). Highlighting of SVG and MathML content in text/html was wrong, too, since the old parser knew nothing about foreign content in text/html.

Consider the following highlighting by the old parser:

<!DOCTYPE html> <html> <head> <title>Title</title> <script> var lt = "<"; <!-- var s = "<script>foo</script>"; --> </script><!-- Not quite optimal highlight there. --> <style> /* </foo> */ </style> </head> <body> <p>Entity: &amp; </p>  <noscript><p>Not para</p></noscript> <svg> <title><![CDATA[bar]]></title> <script><!-- this is a comment --></script> </svg> </body> </html>

The first occurrence of </script> is highlighted as an end tag. The content of the SVG title and script elements is treated as if the elements were HTML elements of the same name.

Compare the above to the highlighting performed by the new implementation:

<!DOCTYPE html> <html> <head> <title>Title</title> <script> var lt = "<"; <!-- var s = "<script>foo</script>"; --> </script><!-- Not quite optimal highlight there. --> <style> /* </foo> */ </style> </head> <body> <p>Entity: &amp; </p>  <noscript><p>Not para</p></noscript> <svg> <title><![CDATA[bar]]></title> <script><!-- this is a comment --></script> </svg> </body> </html>

The HTML script is tokenized according to the HTML rules. Note that <-- … --> inside an HTML script is not a comment node! In the SVG subtree, title and script are not special and can have CDATA sections or comments inside them. (The coloring of the HTML script end tag is inconsistent with other end tags, though, due to technical difficulties.)

Better Error Reporting

The old parser highlighted errors so rarely that it was easy to think it was not doing it at all. However, it did indeed have support for highlighting a couple of errors. I am aware of it highlighting doctypes that used XML syntax inappropriate for HTML and highlighting the already mentioned XML-style slash in tags.

To get feature parity with the old implementation, the new implementation had to support at least highlighting the XML-style slash when the use of the slash is wrong per HTML5 / HTML Living Standard. Since highlighting the slash correctly is among the more difficult error highlights and the Java version of the parser (from which the C++ version is mechanically translated) already supported full error reporting since it was originally written for a validator, I thought I could add support for the easier error highlights, too, while at it.

But why stop at highlights without explaining them? I also made the parser attach error messages to the highlights as tooltips. (Unfortunately, Firefox has long-standing accessibility problems with tooltips, so the error messages are not keyboard-accessible at the moment.)

The new View Source implementation produces results like this (note the tooltips):

<!DOCTYPE HTML PUBLIC"-//W3C//DTD HTML 4.01//EN"> <form> <table> <h1>Error test</h1> <tr><td><div>cell<td>another cell </table> <form> <select><select> <div> <p class="foo"id="bar"> <p/> <br/> <h2><h3></h3></h2> <![CDATA[bogus comment]]> <svg> <![CDATA[this is text]]> <div> <![CDATA[bogus comment again]]> <!--foo--bar--> <!-- foo --!> <p><i><b>bold italic</i></b></p> <p>&#x0000;</p> <p>&auml </p> <p>&foo </p>   </a>

Note: The tooltips will have line breaks between multiple error messages in one tooltip when viewed in the View Source window in Firefox. The lack of line breaks in Firefox in other contexts (including this page) is a known HTML5 violation bug.

Off-The-Main-Thread Highlighting

As a consequence of the off-the-main-thread design of the HTML5 parser in Firefox, the highlight computation now happens off the main thread.

Limitations

The above may set expectations too high, so it is important to lower them right away.

This Is Not a Validator!

All the errors you have seen above are parse errors. Parse errors are errors defined as such by the HTML parsing algorithm. There is much more to checking HTML validity than just finding the parse errors.

For example, putting a div element as a child of an ul element or as a child of a span element is not a parse error. In an HTML validator, content model errors like that are detected by a validation layer above the parser. The View Source implementation in Firefox does not have a validation layer at all.

The lack of a validation layer has counter-intuitive consequences. The HTML parsing algorithm avoids parse errors that would be redundant with validation errors. For example, <div<div> is a start tag for an element named div<div. Since there is no such element in the HTML language, the validation layer would catch the error. However, when we do not have a validation layer, the typo goes unreported.

Please do not advertise the new View Source implementation by saying that Firefox now has a validator in the View Source window.

Not All Parse Errors Are Reported!

Even though all the errors that are reported are parse errors according to the specification, not all parse errors are reported.

• Bytes that are illegal according to the encoding of the page are not marked as errors.
• Forbidden characters are not reported as errors.
• Errors that relate to the end of file are not reported.
• Tree builder errors that relate to text (as opposed to tags, comments or doctypes) are not reported.
• Parse errors related to xmlns attributes are not reported.

XML Syntax Highlighting

The old implementation used the HTML tokenizer for highlighting XML source. So does the new implementation. While the tokenizer has support for processing instructions when it is highlighting XML source, that is the only XML-oriented additional capability. As a result, doctypes that have an internal subset are mishighlighted and entity references to custom entities are mishighlighted. This is obvious when viewing the source of Firefox chrome files. However, the mishighlighting should not be a practical problem when viewing source of typical XML files on the Web (to the extent there are XML files on the Web).

Other Known Bugs

The new implementation broke the window title for View Source windows. Also, the highlighting of the end of named character references is off by one.

Release Schedule

The code landed on trunk in time for Firefox 10. However, the landing added quite a bit of code, so it is possible that the code gets turned off after the Aurora uplift. To test the new code, using Nightly is your best bet.

---

Written: 2011-11-04 by Henri Sivonen

Main Page

The following notice applies to this HTML file:

Copyright (c) 2011 Mozilla Foundation

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

HTML5 Parser-Based View Source Syntax Highlighting A new implementation of the View Source HTML and XML syntax highlighting has landed in Firefox. Why? The reason there is a new implementation is that the old implemention was based on the old HTML parser that we want to get rid of. The old View Sour ...»See Ya

Check out this website I found at facebook.com

Check out this website I found at facebook.com ...»See Ya

World Wide Web Consortium (W3C)

facebook
Hi Gaejang, Here is this week's summary for your Facebook Pages: Dampira Quin (Band) 16 monthly active users3 since last week 114 people like this0 since last week 0 wall posts or comments this week0 since last week 24 visits this week5 since last week Send an update to people who like this Visit your Insights Page Promote with Facebook Ads Dogmeat Page 901 monthly active users233 since last week 75 people like this2 since last week 5 wall posts or comments this week16 since last week 1,082 visits this week2,585 since last week Send an update to people who like this Visit your Insights Page Promote with Facebook Ads Learn more about how to update via mobile Statistics and management for additional Pages Thanks, The Facebook Team
This message was sent to gaejang.guk@gmail.com. If you don't want to receive these emails from Facebook in the future, please click: unsubscribe. Facebook, Inc. Attention: Department 415 P.O Box 10005 Palo Alto CA 94303

World Wide Web Consortium (W3C) Send an update to people who like this Visit your Insights Page Promote with Facebook Ads Send an update to people who like this Visit your Insights Page Promote with Facebook Ads Learn more about how to update via mobile Statistics and management for additional Pages ...»See Ya

W3.org (Inline!)

W3C

W3C By RegionAllAustraliaÖsterreich (Austria)België (Belgium)BotswanaBrasil (Brazil)中国 (China)Suomi (Finland)Deutschland (Germany)Ελλάδα (Greece)Magyarország (Hungary)भारत (India)Éire (Ireland)ישראל (Israel)Italia (Italy)한국 (Korea)LesothoLëtzebuerg (Luxembourg)المغرب (Morocco)NamibiaNederland (Netherlands)SénégalEspaña (Spain)South AfricaSwatini (Swaziland)Sverige (Sweden)United Kingdom

• Standards
• Participate
• Membership
• About W3C
• 

Site Navigation

Standards

•  Web Design and Applications
• Web Architecture
• Semantic Web
• XML Technology
• Web of Services
• Web of Devices
• Browsers and Authoring Tools
• … or view all

Web for All

• W3C A to Z
• Accessibility
• Internationalization
• Mobile Web
• eGovernment
• Developing Economies

Community and Business Groups

• Current Groups
• Proposed Groups

Working Groups

• Specifications by group
• Participant guidebook

Member-only Home

• Join a Group
• Get Member Account

Skip

News

W3C Community Convenes for Technical Plenary 2011

27 October 2011 | Archive

Next week, the W3C community meets in Santa Clara, California for TPAC 2011, W3C's annual face-to-face gathering to coordinate both technical and strategic directions for the organization. We anticipate more than 350 people will participate in Working Group meetings, an Advisory Committee meeting, and a Plenary Day organized this year as a participant-driven camp. In addition to two plenary sessions (on Web and Television, and Web Content Interoperability), participants will discuss a variety of breakout topics. Although participation in TPAC is limited to those already in W3C groups, the TPAC proceedings are public and will be made available shortly after the meeting. Follow the meeting on social networking sites with tag #tpac.

First Draft of WebRTC 1.0: Real-time Communication Between Browsers Published

27 October 2011 | Archive

The Web Real-Time Communications Working Group has published he First Public Working Draft of WebRTC 1.0: Real-time Communication Between Browsers. This document defines a set of APIs that enable video conferencing from within an Open Web Platform application. These APIs allow local media, including audio and video, to be requested from a platform, media to be sent over the network to another browser or device implementing the appropriate set of real-time protocols, and media received from another browser or device to be processed and displayed locally. This specification is being developed in conjunction with a protocol specification developed by the IETF RTCWEB group. Learn more about the Ubiquitous Web Applications Activity.

[[posterous-content:pid___0]][[posterous-content:pid___1]][[posterous-content:pid___2]]Last Call: Touch Events version 1

27 October 2011 | Archive

The Web Events Working Group has published a Last Call Working Draft of Touch Events version 1. User Agents that run on terminals which provide touch input to use web applications typically use interpreted mouse events to allow users to access interactive web applications. However, these interpreted events, being normalized data based on the physical touch input, may not deliver the intended user experience. Native applications are capable of handling both cases with the provided system APIs. The Touch Events specification now provides a solution for Open Web Platform applications: the ability to directly handle touch events, and multiple touch points for enabled devices. Comments are welcome through 17 November. Learn more about the Rich Web Client Activity.

Incubator Group Report: Unified Service Description Language XG Final Report

27 October 2011 | Archive

The W3C Unified Service Description Language Incubator Group has published their final report. The mission of the Unified Service Description Language Incubator Group was to work on the already existing proposal for USDL in three directions: investigate similar approaches and relate them to USDL, reshape the specification to align it with W3C and feedback that was collected, and prove practical relevance by creating reference test cases by various partners. During the XG's lifetime, the group shifted the focus away from working on the language itself in order to better concentrate on use cases and adoption. The Incubator Group Report therefore contains a comprehensive overview and assessment of other languages, specifications and approaches that were considered to be related to USDL. The report also contains a description of our reference test cases and their implementations, a list of issues and ideas of improvement for the next version of USDL, and a statement from some partners about USDL. It concludes with the recommendation to follow up on the USDL specification in form of a Working Group, among others.

This publication is part of the Incubator Activity, a forum where W3C Members can innovate and experiment. This work is not on the W3C standards track.

Schedule, Speakers, and Sponsors Announced for W3Conf Developer Conference

21 October 2011 | Archive

W3C announces today the speakers and the schedule for W3Conf, W3C's first developer conference, in the Seattle area on 15-16 November 2011. W3Conf will feature presentations by renowned experts on mobile development, layout, script libraries, graphics, security, and Web gaming, and representatives from major browser and authoring tool vendors. The talks will focus on technologies you can use today, with a glimpse of the future; this is about developers, not products. Registration is open, with early bird rates available through 31 October. W3C would like to thank Microsoft for making this conference possible, and express our appreciation to Platinum Sponsor ATT, and Gold Sponsors Adobe and Nokia.

More news…

Talks and Appearances

• 2011-11-10 (10 NOV)

  Web content vs Web applications - do we want information or programs?

  by Olle Olsson

  J. Boye Aarhus 11

  Aarhus, Denmark

• 2011-11-11 (11 NOV)

  Adopting HTML5 for Television: Next Steps

  by Philipp Hoschka

  2nd FOKUS Media Web Symposium 2011

  Berlin, Germany

• 2011-11-15 (15 NOV)

  Juridiska tjänster via webben - ett samtal

  panel features Olle Olsson

  Juridiska tjänster via webben - drivkrafter och överväganden

  Stockholm, Sweden

• 2011-11-23 (23 NOV)

  HTML5-Tag 2011

  by Klaus Birkenbihl

  HTML5-Tag 2011

  Berlin, Germany

Events

• 2011-11-08 ( 8 NOV) – 2011-11-10 (10 NOV)

  W3C Social Business Jam

  Online

  Supported by IBM

• 2011-11-15 (15 NOV) – 2011-11-16 (16 NOV)

  W3Conf: Practical Standards for Web Professionals

  Seattle, Washington, USA

  Primary Event Sponsorship from Microsoft

• 2011-11-16 (16 NOV)

  W3C members meeting in Korea

  Seoul, Korea

  Hosted by W3C Korea Office

• 2011-11-17 (17 NOV)

  W3C HTML5 Day in Korea

  Seoul, Korea

  W3C Korea Office

• 2011-12-05 ( 5 DEC)

  Website Accessibility Metrics

  Online

• 2011-12-05 ( 5 DEC)

  Website Accessibility Metrics

  Online

• 2011-12-06 ( 6 DEC) – 2011-12-07 ( 7 DEC)

  Linked Enterprise Data Patterns: Data-driven Applications on the Web

  Cambridge, MA, USA

  Hosted by W3C/MIT

• 2012-04-16 (16 APR) – 2012-04-20 (20 APR)

  WWW 2012

  Lyon, France

• 2012-04-22 (22 APR) – 2012-04-24 (24 APR)

  Global INET

  Geneva, Switzerland

• 2012-05-13 (13 MAY) – 2012-05-15 (15 MAY)

  AC Sophia-Antipolis 2012

  Sophia-Antipolis, France

The World Wide Web Consortium (W3C) is an international community that develops open standards to ensure the long-term growth of the Web. Read about the W3C mission.

Jobs

Marketing and Communications for W3C Business Development

Web Accessibility Engineer

W3C Blog

• The W3C Social Business Jam is a few days away!

  5 November 2011 by Harry Halpin

• Interview: Filament Group on HTML5 and Design

  27 October 2011 by Ian Jacobs

• Some notes on the recent XML Encryption attack

  24 October 2011 by Thomas Roessler

Validators, Unicorn, and Other Software

• Unicorn validator
• HTML and markup validator
• CSS validator
• mobileOK checker
• W3C cheatsheet
• More Open Source Software

W3C Sponsors

Gold

Silver

W3C Member Testimonial

Business Directory UK

Cylex is an international IT company who provides free B2B and B2C solutions. Our mission is to create useful business directories using the latest technologies and standards.

Footer Navigation

Navigation

• Home
• Standards
• Participate
• Membership
• About W3C

Contact W3C

• Contact
• Help and FAQ
• Sponsor / Donate
• Site Map
• Feedback (archive)

W3C Updates

• 

Copyright © 2011 W3C ^® (MIT, ERCIM, Keio) Usage policies apply.

W3C W3C By Region All Australia Österreich (Austria) België (Belgium) Botswana Brasil (Brazil) 中国 (China) Suomi (Finland) Deutschland (Germany) Ελλάδα (Greece) Magyarország (Hungary) भारत (India) Éire (Ireland) ישראל (Israel) Italia (Italy) 한국 (Korea) Lesotho Lëtzebuerg (Luxembourg) المغرب (Morocco) ...»See Ya