you can refer to this plunker:
my plunker
To reproduce this issue just click on the second row ('Project Manager - phase 10') and click on the 'click me' button. This one should delete the current row selected.
Try it on Firefox or IE and all should work fine. Then try it on Chrome (my version is the 65.0.3325.181) and the row you selected doesn't disappear.
So, since they closed the discussion I had opened on their Github page I would like to know if you are able to reproduce this issue (so it's not just my problem)and if you have a solution (maybe someone already encountered this and solved it in some ways). Actually I cannot use the UI-Grid on Chrome for that...
I don't get why I must put some code here after the plunker, since I have like 4 files in it :-)
Ok, it seems it happens just on my pc (an just for my profile). I'm not able to reproduce it on others Chrome versions. I haven't any idea on the reason of this issue but... I actually don't care if it shows up just for me. It would have been a bigger issue if it was for all clients that need to use my application.
Related
I'm using react-select to create a dropdown for an open-source application which uses React/Redux and Electron. I'm using the bog-standard example code provided by react-select for this. However, when running, while the select box shows, clicking it seemingly does nothing. The dropdown that's meant to appear does not. When inspecting the HTML sources, it shows that when it's clicked, something does appear in the HTML, but this isn't visible in the app.
This is quite a large application and I don't know how much value there is in posting snippets of code; this one file alone is 500LoC. Does anyone have any ideas why this might be happening though?
The problem was the "overflow" option of the CSS was set to "hidden" by default. Setting this to "visible" in the CSS resolved this and now I the box appears as intended.
If anyone else has a similar issue, pause the application at runtime using the "debugger" command in console and check the CSS stylings of the element in question. I found this by accident but could help for future!
I had my app working just fine a few days ago and then I noticed the first problem. I had to tap twice in order to make a button go to the next screen. Also happened to the checkBoxes. Had to tap twice to make them change.
But now it got serious. Since yesterday when I tap on a TextField the app freezes and then crashes.
The only significant changes I remember I did were 2: I uploaded an image for the App Icon and I edited the TitleArea UIID. I removed the TOP and BOTTOM margins. It also affected some of my label and button UIID, because now they don't show on the device
When I run the simulator, the doble tap also occurs, but the TextFields work fine and the Button and Label UIID look the way they should.
Any ideas why this happens?
I am right now working with old versions to try to determine the reason, but no luck so far. Thanks
Use a solid color rather than a gradient with the same colors. Gradients are slow and problematic across platforms so you are paying a lot for something that you aren't even using.
We'll need a better test case to reproduce crashing, I think that what you initially saw when you submitted the issue was a regression in the text input that we since resolved in the build servers.
I'm having problems in several versions of Chrome when trying to scroll through a short (25 item) list in my app. The screen smears like so:
I've stripped the controller and ng-repeat element so that there are no watchers whatsoever. It's simply adding binding for basic attributes.
I'm also using angular ui-router, and this is inside of a ui-view.
Problem is somewhat consistent in Chrome and shows up in Safari as well. No problems in Firefox (that I can tell). Have not tested in IE.
Any idea what is causing this behavior?
EDIT
Also potentially noteworthy: this goes away on my laptop (MBP) if I plug in an external mouse. Not sure why. It is a problem on other machines too though, so not specific to my setup.
I'm able to reproduce the behavior consistently by setting height: 100% on any element being used for ui-view. I had originally done this to allow for pushed (but not sticky) footers, but will need to find a workaround.
Removing height: 100% from the ui-view elements solved this for me.
My whole application freezes when I'm closing a opened tab. I have a lots of code but I really have no idea why is this happening?...
Any ideas?
I would post some code but there is nothing specific which could help... -.-
It happens on more computers and tested on all mayor browsers.
It's a simple layout form.
verify if you are ot using a duplicated ID in 2 component.
What tab are you closing??? Is it a tab panel component. Keep a debugger pointing the listener which is called on the closing event and debug a little.bit.
And what do u mean by freeze??? U need to share something. It's hard to give a guess for
the questions.
What browser are you using? Is it happening in other browsers? Is a debugger attached?
In my experience IE is "freezing" when there is a lot of layout being built in the page. It's much more sensible than with ExtJS 2.
It seems that due to ActiveX that Firefox can't display the print icon/button on the Report Viewer control in SQL Server Reporting services. Has anybody figured out a way to work around this or gotten this to work?
If it's not possible, does anybody know of a way to add a standard button that would trigger the print behavior on the report viewer control?
As you state, the print functionality is ActiveX, so it will not work in Firefox.
You could place a button in the "msrs-buttonHeaderBackground" div using a javascript button.
I found the div using the firebug firefox extension - it's great.
You could possibly find the other divs you'd like to hide and put them in a print style sheet, so they don't show up when going to print.
http://www.456bereastreet.com/archive/200709/how_to_create_an_unobtrusive_print_this_page_link_with_javascript/
I agree with the author that ctrl-p could simply be pressed for a similar result instead of adding a button - but the print style would still help in that.
You know what...I just realized something. You will not be able to print a page that is more than one page! Ouch.
I know this is a very old questions, but we came across this and chose the following solution.
We downloaded an IE Tab extension(this is one there are several more) for FireFox and then configured that extension to use IE to render the report server URL by default.
You could easily create a how-to web page,pdf, or maybe even create a dummy report that shows the instructions on how to do this to your end users and then you're all set.
So now every time the report server website is accessed it's being rendered in IE so the print button shows up. Every windows machine already has IE so no compatibility issue there, unless you're not using windows. :)
My best suggestion would be from within Firefox export it to PDF and then print it from your PDF viewer. In my experience this is a better way to print the reports anyway.
Hope that helps!