[Webkit-unassigned] [Bug 73215] [Qt][WK2] Split QWebPermissionRequest into QWebSecurityOrigin

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Feb 15 05:35:51 PST 2012


--- Comment #56 from Adenilson Cavalcanti Silva <savagobr at yahoo.com>  2012-02-15 05:35:50 PST ---

Thanks for the comment.

I thought about friend-ing both classes (since this would help to remove some boilerplate code i.e. the setters/getters), but this poses a question: what happens if other class got to use QtWebSecurityOrigin? 

This would force any user to also become a friend (thus breaking data encapsulation and inspiring layer violations). 

That would not be *that* different about how the current trunk code is (i.e. QWebPermissionRequest has basically the same code that was moved to QtWebSecurityOrigin).


Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list