Any shot of extracting just the Vimeo JS portion of the code to its own
Sprockets manifest file? You could then choose to omit it from uglifying
(or whatever part of the asset pipeline it is choking on) or if you get the
ok from the client, it might be easier to step through the minified code
and debug it outside the whole app’s JS bundle.
Worst case though, you can leave it inline and unminified without fully
disabling the asset pipeline.
On Fri, Mar 2, 2018 at 19:01 Scott Olmsted <solms...@gmail.com> wrote:
> I maintain a couple Rails 4.0 sites (written by someone else) that use
> has stopped working at some point in IE11, if it ever did (though it
> probably did, otherwise there would have been complaints earlier).
> If I use ngrok to access in Windows 7/IE11 my development version running
> on a Mac, the code works. It's when it's bottled up by sprockets that it
> I'm halfway proficient with the Developer Tools in Chrome, not so much in
> Windows, though I'll get there. But the code is jammed together, not for
> human consumption.
> I've already fixed some gnarly code problems and the client is getting
> freaked about costs.
> I guess I could turn off the asset pipeline in production. Any other
> suggestions for how to figure this out?
> SD Ruby mailing list
> You received this message because you are subscribed to the Google Groups
> "SD Ruby" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sdruby+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
SD Ruby mailing list
You received this message because you are subscribed to the Google Groups "SD
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.