Comments for Isotoma Blog

Comment on HTML5 input type=number and decimals/floats in Chrome by David Leinweber

David Leinweber — Mon, 12 Mar 2012 19:21:54 +0000

It looks like some of comments did not show up because they were HTML tags. You add “novalidate” to the form tag, and “formnovalidate” to the submit input.

Comment on HTML5 input type=number and decimals/floats in Chrome by David Leinweber

David Leinweber — Mon, 12 Mar 2012 18:14:49 +0000

If you want to disable client-side validation altogether, you can add the “novalidate” attribute to the tag, or you can add the “formnovalidate” attribute to the .

See here for details: http://www.w3.org/TR/html5/association-of-controls-and-forms.html#attr-fs-novalidate

Comment on HTML5 input type=number and decimals/floats in Chrome by john allsopp

john allsopp — Sat, 03 Mar 2012 22:04:46 +0000

It’s also worth noting that if you want a step value between -1 and 1, then you *must* have a leading 0 before the decimal place

step=.2 will be ignored by all brwosers which support number/range inputs

Comment on HTML5 input type=number and decimals/floats in Chrome by Richard Moore

Richard Moore — Sat, 03 Mar 2012 20:25:17 +0000

Interestingly without the hack of using ‘any’ that would imply that only rational numbers are officially a ‘number’ according to the w3c. Poor old e and pi.

Comment on Content Strategy Forum writeup by Melissa Breker

Melissa Breker — Thu, 10 Nov 2011 05:12:31 +0000

Thanks for covering the key points of the conference!

It’s true, we often think about the “users” experience, and yet we don’t think about our own experience as editors and curators of content.

Also, I really like the idea of curiosity and asking “Why”. I find this to be the case with the clients that I work with.

Thanks again,
Melissa

Comment on Practical collective.xdv by Ross Patterson

Ross Patterson — Tue, 16 Aug 2011 20:04:06 +0000

Maybe this is an older post, but shouldn’t it be updated to reflect that Diazo is the new name for xdv?

Comment on Practical collective.xdv by Laurence Rowe

Laurence Rowe — Tue, 16 Aug 2011 12:09:51 +0000

Thanks for this write up! I’ll just note that for those using Plone 4.1 they should be looking at http://pypi.python.org/pypi/plone.app.theming and http://diazo.org (think of diazo as xdv 2 and plone.app.theming as collective.xdv 2.) Plone 4.2 will include plone.app.theming out of the box.

Comment on UX Lx: Day 1 by Paola Kathuria

Paola Kathuria — Thu, 16 Jun 2011 10:31:52 +0000

Great write-up and a very interesting read. After your tweet, and after my raving about Twitter and Facebook, I’ve realised today that finding out what my friends are up to seems to have used up the time I’d read articles or books. :-/

Comment on Improving Harvest using seductive interactions by Karen at Harvest

Karen at Harvest — Mon, 16 May 2011 15:37:22 +0000

We are honored to be the subject of this UXLx workshop, and we’re thrilled to hear that you think we’re “the best time tracker I’ve used”. We appreciate this detailed wrap up of the workshop, and the dedicated time and focus on what we could do to improve our app. We’ll certainly have the team take a look at these suggestions – you make some very interesting points. We’re always open to ideas, improvements and feedback, and thanks for letting us know what would make Harvest better for you!

Comment on Setting the modification date of an Archetype object in Plone. by Ross Patterson

Ross Patterson — Tue, 15 Feb 2011 23:53:36 +0000

Thanks for blogging about this, this is one of the little gotchas that people like me who find the solution and don’t blog about it should be flogged for.

As a bit of refinement, reindexObject actually won’t set the modification date if the “idxs” argument is passed in limiting the indexes to be updated. As such, you can avoid this problem without the obj.__dict__ lambda hack by just doing obj.reindexObject(idsx=['modified', ...]) where “…” should continue the list of what you want to modify.

Thanks again!