| Summary: | ResourceErrorBase::compare doesn’t call the right platformCompare override | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | mitz | ||||||
| Component: | Platform | Assignee: | mitz | ||||||
| Status: | RESOLVED FIXED | ||||||||
| Severity: | Normal | CC: | ap, beidson, berto, cdumez, cgarcia, commit-queue, danw, gustavo, mrobinson | ||||||
| Priority: | P2 | ||||||||
| Version: | 528+ (Nightly build) | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Attachments: |
|
||||||||
|
Description
mitz
2014-07-24 10:01:25 PDT
Created attachment 235500 [details]
Call ResourceError::platformCompare
Created attachment 235503 [details]
Call ResourceError::platformCompare
Comment on attachment 235503 [details]
Call ResourceError::platformCompare
Do we ever compare errors? What does that even mean? Looking at these methods, I want to delete them, not to fix them.
(In reply to comment #3) > (From update of attachment 235503 [details]) > Do we ever compare errors? I don’t see anywhere in WebCore that we do. > What does that even mean? Checking whether two errors are the same ;-) > Looking at these methods, I want to delete them, not to fix them. Yeah, I’d rather do that if possible. operator!= turned out to be used in comparing authentication challenges. Fixed in <http://trac.webkti.org/r171600>. |