Forums : Feedback Forum
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
info@openhub.net
Global css classes?
So when you embed the project basic stats widget, it creates a block that styles, among other things, body, img and anchor. This, predictably, ruins the formatting on any page into which the widget is placed.
Because other widgets such as the COCOMO project cost calculator do not have this behavior, I assume this is an oversight.
Here is my current documentation:
This is what happens when I add the stats widget, thanks to the block at the beginning:
http://scutil.com/docs/scutil.html
Please fix?
Also, looks like your forum strips out html tags, instead of entity encoding them. That makes it difficult to discuss html defects.
Those links, now that I notice the markdown:
Current docs: link
Broken after widget: link
As per our IRC conversation, we'll tackle:
- The basic stat widget's global css bug.
- Add a cocomo salary url param.
- Fix the negative h3 margin css problem.
Thanks again for helping us out w/ these bug reports.
Awesome, thanks
Hi John,
These fixes have been deployed. To change the default salary in the cocomo widget, include a 'salary' param to the widget .js
href. Example:
http://www.ohloh.net/p/316896/widgets/project_basic_stats.js?salary=80000
Good luck!
All fixes confirmed. Thank you.
On second thought, negative. You added the salary parameter to the wrong widget. It's the cocomo widget that needs it, not project basic stats. :D
Sorry it took me so long to notice that.
Actually, now it's working again this morning. So, last night when I said negative, I may have just been facing caching issues.
You know, it was, but it seems to have regressed. The style tags have returned, and the breakage with them.
Right now I have a problem with the Stats Widgets: It changes the fonts of the whole html site that contains this widgets.
You've found the right forum entry. The reason for the problem is visible if you just load this URL and look at the beginning of the script:
http://www.ohloh.net/p/316896/widgets/project_basic_stats.js
Currenlty, you can make a workaround by using javascript to reset the body style. But thats not really nice, because for a fraction of a second the website has a different style.
Is this bug
going to be fixed soon?
Greeting y'all.
Sorry about the delay. Your suspicions were correct: the fix I had applied originally got reverted by a subsequent commit - so the bad css
behavior returned.
I've re-applied the original fix and thereby fixed the offending, globally-scoped css rules. Thanks for your patience!
Thank you. Fix re-confirmed.
A side note: that you use such common terms as gadget
for your styling is a bit concerning. These widgets stand a pretty good chance of colliding with other style sets. Have you considered using names like ohlohwidget instead?