On 6 déc, 15:28, Julien <[email protected]> wrote: > On 6 déc, 12:30, Colin Law <[email protected]> wrote: > > > > > > > > > > > On 6 December 2010 11:03, Julien <[email protected]> wrote: > > > > On 6 déc, 09:53, Colin Law <[email protected]> wrote: > > >> On 5 December 2010 22:44, Julien <[email protected]> wrote: > > > >> > exact same poltergeist for me on rails 3.0.1 and ruby 1.9.2. It adds > > >> > some visible space in browser but completely invisible in the > > >> > generated HTML. > > > >> > it seems to be when the partial starts by a tag (like "<form ...>"). > > >> > It's not a space but a linebreak. If partial starts by basic simple > > >> > text it's fine. > > >> > I checked my ruby source files encoding and it's plain good utf8. > > > >> > The generated html may look exactly the same using 'source>view' in > > >> > both cases but i'm wondering if there might be some fancy digits > > >> > making this linebreak. > > > >> If the html (and javascript and css) are the same then it must render > > >> the same, that is all the browser has to go on. Copy and paste the > > >> html into a text file for each case and then do a file compare. Also > > >> if you want to see where the extra space is coming from use firebug in > > >> firefox and you can see which div or whatever the space is in and how > > >> the area is styled. > > > >> I note that the OP was not heard from again after he was asked to > > >> check the generated html in this way (with the request re-inforced by > > >> Marnen as it appeared he may not have understood that it was the html > > >> that was to be compared). > > > >> Colin > > > > Hi ! Thanks for reply, i have news: > > > In Firefox, the generated html seems exactly the same, but in Chrome, > > > i can see an extra-digit. > > > Screen:http://lh4.ggpht.com/_Hc_PJsJ5czI/TPy9KFd3RsI/AAAAAAABNIc/bApGqfK32fE... > > > Well I have to apologise for suggesting that if the html looked the > > same then it would render the same. I had not allowed for > > non-displaying characters. I wonder whether you are on developing on > > windows? I seem to remember a problem with <%- -%> that the - > > removed the LF but not the CR in files with CRLF line endings. > > > Colin > > Yep, Windows. When i print special chars in Komodo, i see LF ending > each line, but no CR. I'm really not at ease with those file format > issues, can't be really helpful on that, sorry :(
Confirmation of my second guess: It's Komodo Editor, adding ugly stuff. I've open and added some files in the projects using Radrails and everything is okay. Though i have no way to correct files corrupted by Komodo (open and save doesn't do the trick). Damn Komodo!!! And maybe some other text-editors generate the same kind of horror. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
