I know a lot of users had faced the issue. Did somebody solve this one? Maybe Chrome developers addressed this somewhere?
It's clear from the screenshot, but I'll spell this:
Chrome is misplacing string numbers time to time. And the misplacement is fixed through the file, it's 2 lines miss in this particular case.
Ok, the one way is to simply edit debugging source right in the middle of the process in Chrome (in my case it's: to add 2 empty lines in the beginning of the file).
But I hope someone can advise a better solution.
Related
Hiyah!
I'm sorry for this strange post, just need help articulating my thoughts into something practical. I really could use an extension to basically select any part of the browser window and use it as a floating window (always on top of other windows).
It'd be awesome if something like this existed and I'd love a name in that case! If not, maybe any of you know of similar open source projects that I could take a look at? I'd try to write my own extension if there's nothing like that, so basically could use any keywords to simplify my research. I've been learning full stack web dev for a few months now, so I think it's in realm of possibilities for me.
Thanks for your time!
As highlighted by the screenshots above, the regex checkbox of PhpStorm's find window is no longer visible by default. This is annoying, because I cannot always see, whether a regular expression is narrowing my search or not. I already googled for a solution, but I cannot seem to find one.
Does anybody of you know how to "fix" this?
Thanks a lot in advance :)
Edit: In case you need to know, I am working on a Mac.
It's a bug in 2018.1.
https://youtrack.jetbrains.com/issue/IDEA-188790 -- ticket status says fixed ... but target version is only 2018.2.
Try asking there if the fix will be included in 2018.1.3 or so .. or will it be in 2018.2 only.
This is the first time I am trying to contribute to Mozilla. I went through several articles and documentation/resources to get a hang of what could be the best first steps to get started. I started off from this page http://whatcanidoformozilla.org1 and chose to start off with Java.
On initial tinkering I was taken to https://wiki.mozilla.org/Mobile/Get_Involved and eventually https://wiki.mozilla.org/Mobile/Fennec/Android/Suggested_workflow resource suggested that the best way to get started with it would be to pick up some simple bug and propose a patch for it.
So then I went to http://www.joshmatthews.net/bugsahoy/?java=1&simple=1 and this specific bug drew my attention. The description of the bug mentioned this :
There are some methods that we share (or can share) across our DB
implementations, like appending PARAM_SHOW_DELETED, PARAM_LIMIT, or
PARAM_PROFILE.
These are currently spread across LocalBrowserDB, TabsAccessor,
URLMetadata, and so on. It'd be nice to clean these up.
Question 1. Now how do I get some more context on what exactly is the bug and what is required to be done ?
As of now there seems to be 2 patches already submitted from what I understood (and please correct if my understanding is wrong here). So to get some context about the bug I went ahead and opened up the first patch submitted here.
It gave me some idea as to at least where exactly is the code itself that needs to be fixed. And I found it here
Question 2. Am I on the right track on how to figure out the code that needs to be fixed ?
Question 3. Even after reaching the DBUtils.java file I could not find any documentation about what the class basically does, or where does it fit into the whole picture. Could someone please help me with this, as to how do I figure out what a class is supposed to be doing etc. or at least some documentation around it?
You're on the right path. Basically, the What Can I Do For Mozilla website is a quick and easy way to let you discover projects you might be interested in, so it's the first gateway to the coding contributions.
That said, you did good in picking a bug to start off. However, as you saw the bug was already being worked on by somebody else (marked as Assigned). Your best bet is to find some new "good first bug" to work on. This might be a complicated task, as Bug's Ahoy shows only a few not owned good first bugs.
You should try to get in touch with the Fennec team, either via email or IRC (the latter for quicker responses).
Now, to answer your questions, in a more general way
Question 1. Now how do I get some more context on what exactly is the
bug and what is required to be done ?
Usually, this should be described in the first comment in the bug, on Bugzilla. If that's not the case, feel free to drop a message there and ask for more directions. You can also flag the reporter or the mentor of the bug using the needinfo functionality, as they are usually better shown.
As you can see, somebody asked for more info in comment 1 and some new directions were given.
In general, you won't find a patch with code on the bug itself, but you might find links to files and more precise directions on what to change and how. If not, again, feel free to ping the reporter and/or mentor.
Question 2. Am I on the right track on how to figure out the code that
needs to be fixed ?
You're on the right path. In general, if there are no links to files or DXR on the bug, but some code is mentioned, you can look it up using DXR, as you did.
Question 3. Even after reaching the DBUtils.java file I could not find
any documentation about what the class basically does, or where does
it fit into the whole picture. Could someone please help me with this,
as to how do I figure out what a class is supposed to be doing etc. or
at least some documentation around it?
What I usually do when navigating the Firefox code and need some more background on a not so well documented class, is browse the change log for that file, clicking on the Log button in the top-right panel on DXR (when displaying the file). It will show you a list of bugs that affected the file. You can even trace back the original file that implemented it, to get more context.
On the other hand, if you're only interested to the history of a single line of code within a file, then the blame tool is your friend. It tells you who last touched the line, the changeset and the related bug number. That is also accessible from where you can find the Log, here.
In the case of DBUtils.java, however, it looks like the class just holds some utility functions for database access.
To see how something is being used within the Firefox codebase, you can still use DXR. Here's a sample search for the DBUtils object.
When I type a style in the CSS panel in Chrome developer tool, the developer tool deletes every 2nd or 3rd letter that I type. For example, if I try to type "border-bottom", I would end up with something like "brder-bttom" and it would be almost impossible to type fully unless I type amazingly fast or slow (one letter by one). I think autocompletion is trying to override my input because when there is no suggestion, I can type fine.
If anyone knows a solution or has the same bug, please let me know.
I'm using Chrome 23.0.1271.97.
This looks like a manifestation of http://code.google.com/p/chromium/issues/detail?id=133789 that I've never had a chance to reproduce (and it's only the second report so far).
We had this bug about a year ago, due to the regressed behavior in Chromium, but the offending change was reverted. Please comment on the said issue by pasting the contents of your chrome://version/ and perhaps some steps to reproduce this.
I'm kind of new to using HTML/CSS for real, so this maybe a stupid question.
My problem is a persistent whitespace on top of the page. At first I thought it was something about margin or padding, as suggested by Google and StackOverflow, but as far as I can tell it was nothing of that. I narrowed it down to a piece of text that is being added right after the opening body tag.
Here's what I mean:
If my code on the file is (simplified, but this is enough to cause the effect):
<html><body><p>text</p></body></html>
When I open it in Chrome and use the developer tools to see the elements, it's like this:
<html><body>""<p>text</p></body></html>
If I delete the "" it renders flawlessly. Right now I have a couple of lines of Javascript to remove the "" from every page, but that's obviously not ideal.
Also worth of note is that if put no tags in the body, like this:
<html><body>text</body></html>
Then no "" is inserted.
Besides Chrome, I've tested on Firefox and IE9, same thing happens. What am I missing here?
Thank you.
Thanks. Your comments were great. I had no script, just bare HTML, but as Jon pointed out, it's dynamically generated. Once I realized what was involved (I admit I should have realized it sooner ...) it was easy to find the answer:
Django template inheritance breaks site layout
It's solved. Thanks again.