Oh, I found a bug in `w3m-search-for-next-image-boundary'. I'll fix it within tommorow. Sorry for my fault.