![]() ![]() ![]() ây là cách t ng sp xp du trang trong Safari vi SafariSort. Rt may, tin ích ca bên th ba cung cp mt gii pháp tt. Because I have iOS devices I don't want to buy additional things that are just catching dust all the time, and spend a couple of hundred bucks or maybe ever more just to get a decent range of Android devices. Safari là mt trình duyt web ph bin và có nhiu kh nng, nhng nó li thiu mt tính nng quan trng: kh nng sp xp du trang. so on mobile we don't test on Android most of the time because we don't have a device lab at hand, so we just hope for the best to be honest. It's Gecko and Blink of course, and WebKit. I would say it's more about engines than browsers nowadays. Some strange IT policies where they still rely on IE11 internally. For the startup I mentioned, the clients are mostly from the banking industry and large corporations. It's mostly small API details here and there that you have to work around and dig deep to fix. I feel like this is kind of a golden era for being a web developer just because there's so many standards that have been agreed upon and implemented widely. Taiau Safari keistai trksta vienos svarbios galimybs: galimybs riuoti. In those days things were a lot worse browser support. Kaip automatikai riuoti ymes Safari, skirtoje Mac, naudojant SafariSort Apple Safari iniatinklio narykl leidia lengvai pridti ir naudoti ymes, o dl galimybs sinchronizuoti su kitais Mac ir iDevices renginiais tai yra populiari parinktis. But I've been doing web development since I was a teenager. Sometimes they implement things that are not standards and they sort of create a de-facto standard. Like I said it's sort of a guessing game as to what Safari has implemented of a standard. Think back to Safari issues, more missing or implemented by different/inconsistent? It seems like they're a little more selective about what they implement and don't implement all standards completely. It's kind of always a guessing game as to what they've implemented and what new standards they've decided. So there's so much support behind WebKit, but Safari sort of does their own thing. I think Safari is just a wildcard because its development exists sort of outside the rest of the other browsers. Occasionally we use a Web API that's a little arcane, like DOM MutationObserver for example, but I think that has such good browser support that it's pretty good. Have been resolved with the grid system that we're using. ![]()
0 Comments
Leave a Reply. |