Started working on Firebase database just recently, and node property value is getting truncated.
Which is why sometimes, it's difficult to understand the type of value.
For e.g. the below value are all strings, however, since the ending quotation is not showing, it's confusing.
Also one value is not fully visible.
Chrome: 72.0.3626.121
Edge 42.17134.1.0
Looks OK in Firefox 65.0.1
Windows 10 64-bit
Is this a browser issue? I'd like to work with Chrome.
This indeed looks like a browser-specific rendering issue. I have it in Chrome too occasionally, but aren't too bothered by it (since the data is stored correctly).
It might be worth filing a bug report, so that the UI engineers who build this know that this occurs on a specific browser.
Related
When I try to delete or edit a node in my realtime database, I always get the info that I have to select a key with lesser elements to change something, else it is in read-only modus.
But when I click a low level node, nothing happens. So I actually can change nothing in my DB from console :(
A week ago I didn't see this warning and everything works great!
Any idea how I can get back to working version?
I also think the german translation is not very good, because it tells me that I should activate another mode. In English it says, that the mode got activated.
You're mixing three things here:
Your database console switched to read-only mode, which happens when you have a certain amount of data under it.
The warning is badly translated. Please file a bug report for that.
The database console doesn't handle clicks correctly anymore. I already reported that internally last week, and added your report to it. This bug has been fixed internally and will go into production by May 23.
Update 5/24/17:
Problem resolved. Works now.
It seems the ability to click on a child node and promote it to be the top element of the tree is broken. Doesn't work for me either, even on a small database that is not in Read-only & non-realtime mode. I'm almost sure it was working a day or two ago.
I'm seeing the failure when using Chrome. Just tried Internet Explorer. Its works there.
When I try to delete or edit a node in my realtime database, I always get the info that I have to select a key with lesser elements to change something, else it is in read-only modus.
But when I click a low level node, nothing happens. So I actually can change nothing in my DB from console :(
A week ago I didn't see this warning and everything works great!
Any idea how I can get back to working version?
I also think the german translation is not very good, because it tells me that I should activate another mode. In English it says, that the mode got activated.
You're mixing three things here:
Your database console switched to read-only mode, which happens when you have a certain amount of data under it.
The warning is badly translated. Please file a bug report for that.
The database console doesn't handle clicks correctly anymore. I already reported that internally last week, and added your report to it. This bug has been fixed internally and will go into production by May 23.
Update 5/24/17:
Problem resolved. Works now.
It seems the ability to click on a child node and promote it to be the top element of the tree is broken. Doesn't work for me either, even on a small database that is not in Read-only & non-realtime mode. I'm almost sure it was working a day or two ago.
I'm seeing the failure when using Chrome. Just tried Internet Explorer. Its works there.
I have a very pretty calendar report that I've created on one machine, that shows my company's daily revenue as a color coded block for every day for the past several years. After finally getting a color scheme down and pretty much finalizing it, I went to test it on another machine - and hit a rather large obstacle.
This is the report that I used as a template:
http://bl.ocks.org/mbostock/4063318
It's awesome. And, inside Internet Explorer 11, it looks fantastic. I never would have expected that copying the code and testing the report would produce a blank page, but there it is. On that page, the calendar report is visible. In IE 11. Copying the code to a new html file and opening it, shows nothing. In Firefox, however, everything is visible. as is.
Now, there's a part of that page that points to "//d3js.org/d3.v3.min.js"
And I figured out that in order to make that work in firefox I had to add the http: in front, so that's not my issue.
I'm literally sitting here at my desk staring at two browser windows open and pointing to the same html file. One contains my beautiful report, one is a completely blank page.
Some cursory google searches reveal that IE 8 or lower have issues with the svg. I can't seem to find any references on someone having a similar issue though. Their situation seems to be that with IE10, you need to specify the height and width, not just one or the other, to make sure everything scales properly.
If I could have my way, I'd just run Firefox on all of the machines that are going to run the report, even if it's just for that one thing! Alas, I am but a mere peasant coder and so I have to make it work. in the dreaded IE.
Are there any svg/html/d3.js coders out there that can tell me another way to spit out the data I'm using so that I can get what I'm looking for?
copying the code and testing the report would produce a blank page
Because you're outputting invalid HTML. There is no html or head element for starters.
Output your code in to a file like example.xhtml and open it in Firefox (specifically) as it's XML parser will very quickly tell you what line and column the first XML parser error is occurring on. You are rendering in standards mode instead of quirks though that does not imply your page meets standards.
var m=(document.compatMode == 'CSS1Compat') ? 'Standards' : 'Quirks'; window.alert(m+'-mode.');
First off I apologize if there has already been a similar question before, I honestly couldn't find any.
I'm currently developing a chat using Firebase and thanks to the decent docs I'm making good progress so far, so this isn't really the issue here. However, while testing I stumbled across a little issue that might possibly be a bug.
For managing presence in my chat, I am pushing values to a location that corresponds to my user's unique ID. This pushed value is then removed on disconnect.
By doing it this way, I can reliably determine a user's status without worrying about his number of concurrent connections to my Firebase (i.e. browser tabs).
This is actually working fine with Firefox, Chrome and Safari, but there seems to be an issue with Opera. When using Opera, if you close the tab in which the chat is running, the value that should be removed on disconnect is not. It will be removed eventually after like 2 minutes or so, but it is taking way too long, considering that the same thing is happening instantaneously when using another browser.
Out of curiosity I've tried the presence example using Opera and I was able to reproduce the exact same behavior. If I open the corresponding Firebase in another tab, then run the example, enter a name and finally close the tab that the example is running in, I can see that the value in the corresponding Firebase is not removed as I close the tab.
I would appreciate if you could tell me if this is just me doing something wrong or if it is actually a bug.
Regards
Muddy
Opera has a different model for page transitions than all other browsers. Most browsers fire events when loading and leaving a page. Opera actually keeps old pages hot in memory in order to make the back button faster. When you click "back" in opera it's actually resuming the old page.
As a result, there's no way for us to know exactly when someone has left a page in Opera. As a result, we're forced to simply wait for a server timeout to determine someone has left.
So, short answer, onDisconnect operations DO work in Opera, but they might take a couple of minutes to take affect. In all other browsers the operations will happen immediately if the connection was terminated cleanly, and after a few minutes if it was not.
I'm using the Selenium 2.0 web drivers to try and login to a page. The following code works with the Firefox webdriver just fine, it finds the fields, fills them in and clicks the button.
driver.FindElement(By.Id("UserName")).SendKeys("name");
driver.FindElement(By.Id("Password")).SendKeys("test");
driver.FindElement(By.Id("btnLogin")).Click();
However, whenever I try to use the internet explorer webdriver it says it is unable to find the element with id == UserName. I tried using By.Name, and By.Xpath as well with valid inputs but I still get the same error saying it can't find the element. I am using IE 9 so I'm aware it may be a compatibility issue, however I can't seem to find any posts or information saying there is a known issue.
I just wanted to see if anyone else was experiencing the same issue, or if there is something I'm not doing correctly that is causing my issue. Also, this is a C# .NET project.
-- Edit --
Apparently it is an issue with IE9, I removed 9 and went back to 8 and the test works. I'm still interested to know if anyone finds out why this happens or if there is a work around.
The current release of Selenium (2.0b2) does not support IE9, however 2.0b3 should be released soon and supports both IE9 and Firefox 4.
This answer may also be relevant for anyone experiencing issues getting 'clicks' to fire with IE9.
A workaround to this is to send a .Click() to another element on the page, so that the browser gets the focus, before attempting to click the link, e.g. it's parent:
driver.FindElement(By.Id("Logout")).FindElement(By.XPath("..")).Click();
driver.FindElement(By.Id("Logout")).Click();