html

Let’s put this puppy to bed

/ bullcitydave / Leave a comment

I don’t want any design critiques. It’s not finished yet. Demo Day is Friday. But I’ve got to say for the record that I’ve never worked so hard on anything. And 70% of my time has been spent on Javascript code, things like figuring out how to get dates to save to Parse and arrays to render directly to the page without loops but just a simple space after commas…and promises to deal with asynchronous events…I didn’t really get the latter working as I’d like. Keep mind I’m just team of one, so I’ve been dealing with:

  • Parse database
  • CSS/Sass styling
  • Bourbon/Bitter/Neas styling
  • Javascript
  • jQuery
  • Underscore/templates
  • Masonry/layout
  • Account management view
  • Splash screen
  • Parse pic list mgmt
  • Flickr pic list mgmt
  • Vine list
  • Backbone framework
  • Responsive design
  • Presentation TBD, somehow encapsulating all of this, and my overall background in coding and in life, in 5 minutes, this coming Friday

So…not quite done yet. But I need to at least put myself to bed. Moksha has already gone to bed.

Advertisement

Coding error fixed #2: Chrome not rendering page at full width

/ bullcitydave / Leave a comment

This was driving me crazy for…well, probably since last weekend’s project. I was using my CSS from last weekend’s project in a test bed for this weekend’s project, and page elements that should have rendered at full screen width or full container width (approximately 960px) were rendering at 600px or 700px in Chrome. All appeared fine in Firefox.

I realized that the main html tag has all of these reserved classes automatically applied to them:


<html class=" js flexbox flexboxlegacy canvas canvastext webgl no-touch geolocation postmessage websqldatabase indexeddb hashchange history draganddrop websockets rgba hsla multiplebgs backgroundsize borderimage borderradius boxshadow textshadow opacity cssanimations csscolumns cssgradients cssreflections csstransforms csstransforms3d csstransitions fontface generatedcontent video audio localstorage sessionstorage webworkers applicationcache svg inlinesvg smil svgclippaths">

Last weekend, in my ignorance, I had named a div class video. This was the problem. Of course, there is no need for this div in this weekend’s project, and it would not have wound up in the actual project repo. It would’ve been a mystery to me why this was happening…and it is still a mystery as to why exactly this behavior occurred in Chrome and not Firefox, but there’s no time to look into this deeper.

Lesson learned: don’t use reserved classes