I don't understand all the comments in this bug... Why the developers don't look at the code an check when the button is disabled?
Anyone can tell us when the button is disabled or when it is enabled? The application check something to show or not the button. What are these conditions? If we have the conditions, we could check better the application. Really the firefox/chrome cache influences to gwibber? Really influences if you are logged in facebook in an external navigator? I think it is an internal design problem if all the questions are true (probably thanks to the great (hehehehehe) oauth protocol without desktop applications support...) -- Can not add Facebook account as add button not displayed after authorisation. https://bugs.launchpad.net/bugs/595265 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
