I'm facing an issue in scrolling datatable.
If scrolling is disabled, the datatable looks like :
But when scrolling is enabled, the columns get distorted & look like:
Infact the text size also changes.
Any workarounds ? I did have a look on http://code.google.com/p/primefaces/issues/detail?id=3361#makechanges . But is there any other workaround ?
Regards,
Shikha
As per the comments above, it is not supported currently.
BR,
Shikha
Related
I have an XtraReport that overflows text on to the next page but occasionally cuts the last line of text from the first page in half when it does.
I would normally handle this with the height property of the text area but I am unsure how to target a specific table row of an XtraReport to work out what the remaining height of the page is to achieve this or whether that would even work in this instance.
I'm rather hoping there's a simple work around to achieve this, please don't go too much out of your way to help out as I won't be investing much development on this.
I don't think there are any settings I have missed within the designer, perhaps there's a golden font size or line height that the reports want to overflow correctly.
Any help or direction would be greatly appreciated, thank you.
If there is no simple way, I will just have to loop through the tr / td tags and see if by manipulating the height I can find that sweet spot, i just worry that it will hide page 1 but still be split on page 2.
It seems to me that you use the ASPx/MVCx -DocumentViewer,
this control shows you a html content which is not suitable for pixel-perfect documents.
I recommend you to try the ASPx/MVCx WebDocumentViewer which is like the the Google Docs shows pixel-perfect document and more convenient with bootstrap and other progressive web frameworks.
here are demo and docs.
I am using JQGrid and I want column drag and drop feature for this I enabled set sortable = true option. Now the problem is when I have scrollbar and trying to reorder the last columns by dragging the UI of header is mess up as shown below. When I click on country column this column placed at other end.
I had fixed my issue... Sorry its my bad... I was mess up with some css of other components.
Thank you Oleg for helping me and also for wonderful grid component.
There is already a similar question asked but there is no response(Draggable JQuery UI scroll issue when using within iframe).
I want scroll to work for the draggable object in IFrame. Please suggest.
Here is the jsFiddle - http://fiddle.jshell.net/Msd7v/29/
Have a look at this http://fiddle.jshell.net/vryz2t1o/1/, I managed to make it work when you are scrolling down. You need to try to figure out scrolling up and you are done.
Does anyone know if it's possible to get the tbody to scroll with the '-webkit-overflow-scrolling: touch' property on an ipad?
Thanks!
I don't think webkit allows overflown tbodys with out setting header and body to display:blocks, and also setting the widths of the individual table cells. Here is a good link on the subject .
That said -webkit-overflow-scrolling:touch will work on anything that is set to overflow. I have a working example on a tbody as well.
I have a textbox that I am attaching jQuery UI's Autocomplete functionality to and I am using CSS to give it a max height via the example here. My problem is that doing this causes the z-index problem that bgiframe solves to come back again, but in a different way. The initial autocomplete menu is above all the controls underneath it, but when I begin to scroll the autocomplete menu falls behind them.
Any suggestions?
EDIT:
This is purely an IE6 bug.
As you can see, after scrolling down the autocomplete falls behind the other controls.
I could solve the problem by replacing offsetHeight by scrollHeight in the following line (from jquery.bgiframe.js) :
height:'+(s.height=='auto'?'expression(this.parentNode.offsetHeight+\'px\')':prop(s.height))+';'+
This change solved the bug for the autocomplete fields with vertical scrollbars. I could not spot any regression in other kinds of dialogs (but I did not run extensive tests).
You need to reverse the z-index order of the form elements (or their containers) using javascript. I.e., "Social Worker" has the lowest, "DX Code" the highest z-index.
You could change the offsetHeight to scrollHeight, like Siggen says, but I have encountered problems when there is only 1 result returned from the autocomplete. The 1 result is squished into a window that only like 2 pxs high.
I found a fix though.
When you have a data.length<2, you should use the offsetHeight, rather than the scrollHeight.
You have to modify autocomplete.js.
Locate this code:
if($.fn.bgiframe)list.bgiframe();
And make it this:
if($.fn.bgiframe){
if(data.length<2)
list.bgiframe({height:'expression(this.parentNode.offsetHeight+\'px\')'});
else
list.bgiframe();
}
Remember, this code should be used in combination with Siggen's fix.
I have used a combination of both parameter for the height like this:
'height:'+(s.height=='auto'?'expression(Math.max(this.parentNode.offsetHeight,this.parentNode.scrollHeight)+\'px\')':prop(s.height))+';'
Look at the max function. Now it is good with no scroll bar (shorter list and longer list as well)
and now the autocomplete component looks perfect in IE6.