Daniel Bratell

The documentation for regressionExp says `ignoring points with invalid values (null, undefined, NaN, Infinity).` so ignoring negative values would also be ok. Not that the documentation seems to be true...

There is a comment in warp_array: ``` # XXX Take into account the extents of the original to determine # target_extents? target_native_x, target_native_y, extent = mesh_projection( target_proj, target_res[0], target_res[1], x_extents=target_x_extents,...

It has broken things. Big surprise. I think stock_img is plotted with a single pixel in the test_stock_img() test which is probably not enough. :)

Not sure what is wrong. The code fails to convert `extent=[-180, 180, -90, 90]` to something useful. I suspect it has something to do with the the corner points of...

Yes, I'm in deep water here. The code change seems to work fine for those areas and projections I'm working with, but clearly this does not work for all projections...

This prevents further optimizations too. It's not uncommon for one pass to emit "let x; x = ...." and if it had been "let x = ..." then the next...

I have found Shift+H in the documentation, which was funnily enough in the hidden sidebar. IMHO there still needs to be a visible way to restore the sidebar

I did not file a support request. It is a report about a flawed UI. Personally I've moved on and am not concerned either way.