Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialDan Boschen
3,822 PointsI am recently getting a consistent "Aw Snap!" error in Chrome after pressing Dismiss from the success flash message.
As of today I am consistently getting a "Aw Snap!" error in Chrome (Version 48.0.2564.97 m (64-bit)) immediately after pressing "DISMISS" from the success flash message in code that worked previously using the guidance in "Flash Messages Using Slim" tutorial. The fail message does dismiss properly after pressing "DISMISS".
This is what I tried:
- I cleared my Cache in Google Chrome- problem still occurs.
- I rebooted the computer - problem still occurs.
- I tried accessing page on Chrome from another computer - problem still occurs.
- I tried accessing page on Chrome from an iPhone - DISMISS works properly!
- I tried accessing page using IE (version 11)- DISMISS does not do anything from the success flash message, but works properly for the fail flash message.
- I went back to this tutorial and confirmed the same behavior.
- I change the CSS such that #feedback.success does not transition back automatically similar to $feedback.fail as shown below. Once I did this the dismiss works properly (although no longer automatically dismisses, which otherwise had worked fine with the orignal #feedback.success CSS).
#feedback.success {
transform: translateY(-100px);
background: #058a00;
-webkit-animation: feedback-in .3s ease-in-out forwards;
-moz-animation: feedback-in .3s ease-in-out forwards;
animation: feedback-in .3s ease-in-out forwards;
}
I also tried increasing the feedback-out time to 30 seconds to see if the automatic dismissal of the message was causing a conflict. The error still occurs with a significantly longer feedback-out time.
I tried running Google Chrome in Incognito mode; problem still occurs.
So I am completely baffled and out of things to try. Any other thoughts? Is this repeatable elsewhere?
Dan Boschen
3,822 PointsDan Boschen
3,822 PointsThis issue went away when I checked again today 2/23/2016. I noticed my browser version (Chrome) is now 48.02564.116m (64 bit) which Chrome reports as being released 2/18/2016. Apparently this was an issue with the browser that they resolved so this can b closed.