Do web browsers consider NAPTR records in DNS resolution?
No, I don't think they do. Why would/should they?
(NAPTR were (are?) mostly used around ENUM and telephony stuff, in tandem with SRV record types, which ones are also specifically not used by browsers - if they were we wouldn't have to need to create HTTPS record types see at bottom)
What are you attempting to do, specifically when speaking about using an URL or data URL?
As for your other comments:
Well, NAPTR lets you specify a URI.
Other records do, too. Including the URI record type (RFC 7553). That no one uses.
On another note, which record types are considered by browser DNS resolvers?
Difficult to be 100% authoritative without having to check all source code of all browsers. Good luck to anyone wanting to do that. I am fairly certain you can discover some skeletons in the closet.
Do also note that:
- browsers are doing DOH now, so potentially retrieving more data/record type than before (one of the argument of DOH, even if minor, is that it allows a "richer" DNS experience as it is then able to ask for anything instead of relying on the OS that provides basically only final resolution that is
A/AAAA records
- there are new record types around the corner,
HTTPS and SVCB, which some browsers/OS already said to use
