Welcome, Pierre.
Thanks for the info. My current thinking is to start publishing on clojure.org
two, or maybe even three versions of the cheatsheet:
(1) no tooltips, just like the one published now, in case people find them
annoying:
http://clojure.org/cheatsheet
(2) tooltips with the title attribute, for those that prefer
web-standards-compliant pages, such as this one:
http://homepage.mac.com/jafingerhut/files/cheatsheet-clj-1.3.0-v1.4-tooltips/cheatsheet-title-attribute.html
(3) tooltips using a modified TipTip jQuery plugin tool, for people like me who
like its look & feel better than (2).
http://homepage.mac.com/jafingerhut/files/cheatsheet-clj-1.3.0-v1.4-tooltips/cheatsheet-full.html
The nice thing is that all three of these are currently generated from the same
program. Not only are those three pages generated, but also several variations
of A4-size and US letter-size PDF files, with links (but no tooltips in the PDF
-- I don't know how to do that if it is even possible). So far, it is still
pretty straightforward for me to add a new symbol or category to the
cheatsheet, and regenerate all of these things in a minute.
There shouldn't need to be any argument over which of these should be "the
one". I say publish them all, with an easy way to get from one version to
another in case you change your mind which one you want to use.
And if I am stretching what a tooltip is meant to be, and thereby join the
ranks of web-standards-heathens who stretch the original intent of these
mechanisms, I do so proudly :-)
Andy
On Mar 25, 2012, at 10:36 PM, Pierre Mariani wrote:
>
>
> On Saturday, March 24, 2012 11:59:49 PM UTC-7, Andy Fingerhut wrote:
> I've tried again using links with doc strings as the values of the title
> attribute, but when the text in Firefox 11.0 it does not honor the line
> breaks in my text, but reflows it. Try it out yourself at [1]:
> [1]
> http://homepage.mac.com/jafingerhut/files/cheatsheet-clj-1.3.0-v1.4-tooltips/cheatsheet-title-attribute.html
>
> Is there a way that Firefox will let me specify where line breaks should go?
> If I put <pre> or <br> tags in the text of a title attribute, those just show
> up literally in the text that the browser displays in the tool tip. I have
> line breaks in the title attribute value in my HTML, but Firefox seems to be
> ignoring those.
>
> Safari and Chrome seem to honor the line breaks in the title attribute, but
> they make the popup windows so narrow that the lines break in the middle, in
> addition to where I put my line breaks, which is better but not great. Is
> there a way to tell the browser to make the popup windows wider?
>
> Andy
>
> This is my first post to the list, so hi everybody!
>
> Andy,
>
> Tooltips are being rendered by the browser itself and you cannot control
> their aspect with HTML or CSS.
> This bug https://bugzilla.mozilla.org/show_bug.cgi?id=358452 seems to be
> related to your issue, and it indicates that the behavior you are looking for
> should be implemented in FF12. Unfortunately, that doesn't fix it for other
> browsers, or older versions of FF.
>
> Sorry if it sounds critical and isn't very helpful at this stage, but I think
> the concept of tooltip is being stretched a little here. The 'title'
> attribute is not meant to contain one or several paragraphs of formatted
> text, and as such I would expect that you may run into more issues like this
> in the future.
> I would personally use DL lists, have each function name in a DT and the
> corresponding docstring in a DD. I would then have a CSS sheet targeted at
> screen and handheld media hide the docstrings, and I would have javascript
> code show them on mouse hover and hide them on mouse out. I think that would
> ensure best semantical fit of content to HTML tags, best accessibility for
> visually impaired people, and reliable cross-browser behavior.
>
> http://htmlhelp.com/reference/html40/lists/dl.html
> http://htmlhelp.com/reference/html40/lists/dt.html
> http://htmlhelp.com/reference/html40/lists/dd.html
> http://www.w3schools.com/css/css_mediatypes.asp
>
> Pierre
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
