21015 2008-09-22 19:58:15 -0700 KURL's getters are inconsitent about returning null or empty strings 2023-05-22 03:40:50 -0700 1 1 1 Unclassified WebKit Platform 528+ (Nightly build) All All RESOLVED INVALID P2 Normal --- 37641 1 brettw webkit-unassigned abarth annevk ap oldest_to_newest 92267 0 brettw 2008-09-22 19:58:15 -0700 KURL's getters randomly return either isNull or empty strings. This is potentially dangerous if some code relies on this. Returns a null string on empty: pass() lastPathComponent() ref() Returns an empty string on empty (although at least some of these will return a null string if the URL is itself null): protocol() user() host() query() path() We can make them all return null strings, all return empty strings, or return null strings only when the URL is itself NULL, and empty the rest of the time (I think this is currently the dominant behavior). 92292 1 ap 2008-09-23 00:05:04 -0700 With any changes, we'll need to check all callers - in many cases, the behavior is not exactly random, even if it is painfully inconsistent. 1956891 2 annevk 2023-05-22 03:40:50 -0700 We no longer use KURL.