Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
 y_grynechko
		
			y_grynechko
		
		
		
		
		
		
		
		
	
			
		
		
			
					
		Hello,
recently the tooltips on the area layer on the maps stopped showing the whole number. It just shows the first couple numbers and '...':
I works fine in IE and Safari. Seems to be some new change or bug. Not sure how to fix it, any ideas?
Thanks!
 Spivey
		
			Spivey
		
		
		
		
		
		
		
		
	
			
		
		
			
					
		Such an annoying bug. Besides @Greg_Oliven's solution, the only other way to fix it that I've found is to adjust with CSS using a custom theme. Something like:
#qs-chart-tooltip > div > div > div.qv-chart-tooltip-inner > div > div > table > tbody > tr > td.qv-tp-template.qv-tp-value.ng-binding.ng-scope > div > span {
    overflow: visible!important;
}
 
					
				
		
 fosuzuki
		
			fosuzuki
		
		
		
		
		
		
		
		
	
			
		
		
			
					
		I suggest you open a support ticket with Qlik.
 Greg_Oliven
		
			Greg_Oliven
		
		
		
		
		
		
		
		
	
			
		
		
			
					
		Hi @y_grynechko, I am seeing the same thing. Have you figured out a solution? A workaround I have found is to go to the map area layer Options and change the Tooltip from Basic to Custom. There, select Hide basic rows (the ones that aren't displaying right), and Add Measure (e.g. the same measure as Color by measure).
 Spivey
		
			Spivey
		
		
		
		
		
		
		
		
	
			
		
		
			
					
		Such an annoying bug. Besides @Greg_Oliven's solution, the only other way to fix it that I've found is to adjust with CSS using a custom theme. Something like:
#qs-chart-tooltip > div > div > div.qv-chart-tooltip-inner > div > div > table > tbody > tr > td.qv-tp-template.qv-tp-value.ng-binding.ng-scope > div > span {
    overflow: visible!important;
}
 
					
				
		
 caiogil1
		
			caiogil1
		
		
		
		
		
		
		
		
	
			
		
		
			
					
		Thanks.
@Spivey 's solution worked for me. It's really a frustrating bug. 
@Greg_Oliven 's solution worked but only show one value per time.
Hopefully they fix this with a update... not sure but probably has a ticket already to fix this. 
 y_grynechko
		
			y_grynechko
		
		
		
		
		
		
		
		
	
			
		
		
			
					
		