Didn't mean to sound gruff. Sorry if I came off that way! I'm pretty sure the IE bug is a known one. I don't personally use this feature -- the line comments have always been sufficient for me. Maybe Nathan can speak to whether this issue is documented/expected.
chris On Wed, Jan 19, 2011 at 9:12 AM, Josh Rubinstein < [email protected]> wrote: > > I have debug_info on while in my testing environment so that I can > test all browsers in a fluid manner...(test Firefox Mac/PC, Chrome, > all versions if IE...then deploy with debug settings off) This is the > first time I have seen this cause such an error with the debug info > being inserted into the CSS file so I thought I would inquire. > > Obviously I would not compile my CSS with the debug info into my > production environment. I thought I made that clear in my original > post. > > Thanks. I seem to have irritated you when my intention was to simply > inquire and relay my findings. Thanks > > > On Jan 18, 11:13 am, Chris Eppstein <[email protected]> wrote: > > Why would you have debug_info on when using any browser other than > Firefox? > > It's adds a ton of bloat to your css file and should be used in > development > > only in conjunction with FireSass. > > > > Chris > > > > On Tue, Jan 18, 2011 at 10:03 AM, Josh Rubinstein < > > > > > > > > [email protected]> wrote: > > > It is my hope that I describe this correctly and that this may help > > > others with this possibly obscure...dare I say bug. > > > > > I discovered a rendering difference between production and staging for > > > my master branch that only seemed to occur in Internet Explorer. With > > > the help of my co-workers we bisected the branch until we found the > > > commit in which the error began to manifest itself. It appeared as > > > though I may have improperly name-spaced my sass and introduced the > > > rendering issue but with further investigation I discovered that the > > > main difference and cause of the discrepancy between staging and > > > production were the settings found in our config/environments/ > > > development.rb file where we set sass config options. > > > > > When I removed the :debug_info => true option the rendering issue > > > magically disappeared. > > > > > Is this behavior others have seen? Can I somehow fix this? I would > > > hate to loose the ability to use FireSass and or have debug > > > information. > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Haml" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<haml%[email protected]>< > haml%[email protected]<haml%[email protected]> > >. > > > For more options, visit this group at > > >http://groups.google.com/group/haml?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Haml" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected] <haml%[email protected]>. > For more options, visit this group at > http://groups.google.com/group/haml?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Haml" 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/haml?hl=en.
