Todd, I know what you're saying with the thumbnail browser, and don't take issue with it.
I just wanted to make sure that what I was seeing was accurate and intended. Not sure what would be best in that area as I'd have loved to show this content in the thumbnail browser but I fully understand the implications. Thanks for an awesome product and for weighing in on my questions. Cheers, Jim On Mon, Mar 16, 2009 at 2:05 PM, Todd Ditchendorf <[email protected]> wrote: > On Mon, Mar 16, 2009 at 7:41 AM, Jim <[email protected]> wrote: >> >> I was configuring the thumbnail plugin to show me thumbnails for a >> particular set of links in a web app I work on. This led to a few >> questions/observations: >> >> 1) A curiosity: I had to write a userscript to modify all of the URLs >> I wanted to thumbnail so as to add the protocol and host to them. Any >> URL the plugin attempted to work with was simply being prepended with >> http:// if it was relative, rather than using the protocol/host of the >> page in question. > > that sounds like a bug. but at least the workaround is easy :| > >> >> 2) A problem: the pages I wanted to thumbnail require that a user be >> logged in. Although I had logged into the website via the SSB, the >> thumbnail browser apparently did not have access to the cookies for >> the site in question because all of the thumbnails came back with the >> login screen we would show to someone who requested the page without >> being logged on. > > i realize this can sometimes suck, but this is intentional, and if you think > about it, the alternative would suck worse. > if the thumbnail plugin shared cookies with the main SSB webviews, you'd > pick up *a lot* of extra, unwanted cookies whenever you used the plugin with > say, google, digg or pretty much any other site. > when u use webkit in your app (like fluid and the thumbnail plugin do) you > have three cookie-handling behavior options (look under the Security Prefs > Pane to see these). So for the thumbnail plugin, the cookie-handling > preference is always 'accept no cookies' to avoid cluttering your cookie jar > (which is shared with Safari and other Fluid SSBs) with tons of junk > cookies. > as has been often discussed here, webkit (by default) does not offer the > ability to partition cookie jars (this is why all fluid ssbs share cookies > with safari, etc), so it's not possible for me to just tell the thumbnail > plugin to use a separate cookie jar (without going to extreme lengths of > developing my own custom webkit or adhoc cookie jar solution, which I am not > willing to do). > the only possible change to this i might make is to add an "Accept Cookies" > preference to the Thumbnail plugin pref pane -- that would allow it to > pollute your shared cookie jar with cookies from the pages viewed in > thumbnails if you wished. > But honestly, i dont think most users would understand the implications of > this, and when it comes to features involving cookies, I definitely tend to > err on the side of caution. > Maybe i could add a user default -- so expert users could change that > setting on the command line? > td > > > -- Jim Auldridge 11012 Lincoln Ave Hagerstown MD 21740 301.582.9050 (h) 240.520.0240 (m) http://www.auldridges.com Religion that is pure and undefiled before God, the Father, is this: to visit orphans and widows in their affliction, and to keep oneself unstained from the world. --James 1:27 (ESV) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "fluidapp" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/fluidapp?hl=en -~----------~----~----~----~------~----~------~--~---
