There is no standard way to serve and view manga even though manga web sites share common requirements, and each manga provider implements a viewer their own. Someday, I thought IIIF might solve this problem. IIIF is a framework and collection of specifications which define ways to serve large(high-resolution) images, resized versions and tiled images, and tell where they are, order to view, attributions etc to viewer applications. It seems designed for libraries, museum and so on, but might help manga providers because both shares requirement that they need serve many images to reader.
So, I did it.
This is a translation of Japanese article "Intersection Observerによるモバイル用スクロールスパイ".
I was impressed by Intersection Observer を用いた要素出現検出の最適化(“Optimization of detect of element appearance by Intersection Observer”. You can see similar article in English here: Intersection Observer API) by Jxck. And then, I implemented scrollspy for mobile by using it(Firefox works the best. Safari also does fine):
Intersection Observer primarily provides a advantage that we can reduce need to watch scroll events. Lazy loading of images seems thought as a typical use case that starts loading images just before <img> elements are in view instead of on page loaded.
Gosuke Miyashita’s Serverspec: The Definitive Guide was published by O’Reilly Japan. The author Miyashita a.k.a. mizzy and @gosukenator is the very developer of Serverspec, so, this book is literally “definitive.”
The book Serverspec focuses the software Serverspec’s backgrounds such as secret of birth, design principles, development attitude and so on as well as overview and advanced usage. Especially it is important that the book describes what Serverspec does and does not and expectations for users and contributors to and not to do. After reading, we can say Serverspec is “opinionated” as often said for Ruby on Rails. …
Probably, you have thought to test HTTP results such like status code, response headers and body, or SQL query results by Serverspec. I have done too. But then you should have felt strangeness like “Is Serverspec responsible for such higher level state? Which resource type should I use? Execute curl command from target server to loopback interface? How about virtual hosts”? After a little thought about attribute of Serverspec, my questions were summarized as “Are HTTP responses and SQL results states of server? By analogizing from Serverspec’s current Resource Types, it tests STATES of servers”.