I am not able to view HTML/CSS within the HTML panel.It is covered by some grey block. I reinstalled Firefox and Firebug but the issue still persists. Can anyone guide me how I can remove this grey block?
As described in the FAQ to Firebug this is not a bug in Firebug, but known to be caused by the following extensions:
Lazarus: Form Recovery 2.3 (seems to be fixed in version 3.2)
Pentadactyl
Zotero
Related
when i go to the any page view-source in Mozilla Firefox browser i have problem that you can see in screenshot...
codes font in view-source of Mozilla Firefox browser are like that
and that's where the problem come from, when i change '-moz-fixed' font it will solve the problem but i always have to do this :(
here in this picture you can see what i am talking about...
apparently it was firefox bug and it fixed by their update updating because i didn't change any things and no longer have this issue
here you can see it's working fine
I am using latest fireFox version and not able to turn on firebug. It is showing deactivated. can anyone help me how to activate it? As I am not able to search xpath.
Firebug is no longer available in Firefox, now replaced by the Firefox Developer Tools. There's a guide for migrating.
What you are seeing are actually the Firefox DevTools. When opening it the first time, there is a hint explaining the transition a little:
Note that even the Firebug toolbar button disappears with the release of Firefox 57. The backgrounds are outlined in a related blog post.
Unfortunately, the DevTools do not provide an XPath search within their Inspector yet. There's an enhancement request filed for this feature, though.
Having said that, you can at least copy the XPath to an element via the context menu:
Furthermore, if you need the XPath for automated testing like Selenium, you can use CSS selectors in most cases instead, which can be searched for using the search field.
I have a Google Chrome problem on macOS Sierra: Image: SVG rendering bug
As you can see in the image above, the SVG background images in the stackoverflow answering section are not rendered correctly. That also applies for the stackoverflow logo and for any other SVG background images.
I solved the problem temporary by deinstall and install Chrome again. The next day I had the same problem. Chrome is up to date on version 56.0.2924.87 (64-bit).
I also have the issue that if I hover over an DOM element in the 'Elements' tab in dev-tools, the element is not highlighted on the page. This was also gone after reinstalling but also appeared the next day again.
Any ideas about these issues?
I think there's a bug on widget on firefox (version 39 on both OSX and Windows). http://ckeditor.com/demo#widgets
When clicking on part of the widget to edit, the cursor is always at the beginning instead of where you click. Cannot move left and right at all. Cursor up would go to the beginning and down would to to the end of the line
Any CKEditor developers can shed any light on this?
You are correct. This issue is caused by a contenteditable bug in Firefox 39. Update your Firefox to 40+ in order to resolve the issue. This is not an issue specific to CKEditor.
My Boostrap framework is working fine on Chrome and Safari. It also is mostly on Explorer and Firefox. However, in Explorer and Firefox, a couple of images on interior pages appear to have an offset applied. The issue will be apparent when viewing the pages:
notagamebook.com/the-author-2
notagamebook.com/excerpts
I have been unable to find anyone else who has encountered the same issue. And I realize a manual fix won't be all that difficult, but I would like to keep the images in the framework and figure out what is happening in case it occurs again in the future.
EDIT
After attempting to fix this issue manually, I have realized it is NOT a Bootstrap issue. Firefox and Explorer are pushing the first piece of content following the page label to the right. It did so even when coding outside of the Bootstrap framework. I tried putting a piece of text as the first item and got the same result.
I've found the solution to this problem: There was a difference in the bottom margin being applied to the title in Explorer and Firefox, pushing the content to the right of the title div.