Possible Tab Bug?

The current bug: Adding an additional tab below another will cause the tab to looked messed up. The work around suggested was to create a page (with new tabs), publish it as a portlet underneath a main tab. Then you will visually see tabs underneath tabs.
The new problem you get with this work around is your content underneath the sub-tab will not show up the first load. You have to click on another tab, then back to the previous tab to show the content.
Another weird thing I ran across having to do with regions and published folders. I found that you cannot set a corrent percentage within regions when folders are added to regions.
For instance; Under a tab, divid a region into two regions. The first region make 5% and the second 95%; now when you add your (folder) portlets underneath both regions you will see when viewing it, that it will show up 50% and 50%. If you take out the folder portlet on region 1, and add a application portlet; everything shows up fine.
I have come across varies things like this, but I will start posting the errors and possible work arounds.

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>The new problem you get with this work around is your content underneath the sub-tab will not show up the first load. You have to click on another tab, then back to the previous tab to show the content.<HR></BLOCKQUOTE>
I noticed this also. (in 3.0.6.7.2 on NT).
What's funny about this is that this is exactly the same as a bug with sub-tabs in the EA release. Maybe the data structure of a sub-tab and a page in a tab is very similar...
null

Similar Messages

Thinkpad S540 possible BIOS bug concerning WOL

I have had a Thinkpad S540 for a few months, and have it installed as dual boot Windows 8.1 and arch linux. After completely shutting the machine down from linux I found that the battery would be down to around 70% charge after three days unused, and decided to investigate this problem since it was not reasonable for a new battery to lose charge at anything like this rate.
By chance I came across a piece of information concerning the issue of disabling WOL (Wake on LAN) on the network interface, since I had seen one report that by default WOL is enabled and this requires power to be going to the network interface even when shut down in order to be able to respond to magic packets to start the machine up when it is shut down.
First I checked the BIOS WOL setting and found it was set to "AC only" by default. So I changed it to disabled. This machine has the latest available BIOS version 1.54.
However on investigating this after rebooting in linux I found that
# cat /sys/class/net/enp3s0/device/power/wakeup
enabled
# ethtool enp3s0 | grep Wake-on
Supports Wake-on: pumbg
Wake-on: g
So WOL was still enabled despite it being set to disabled in the BIOS!
I learned that I can make sure that in arch linux the WOL setting can be changed to set to disabled after bootup by using a udev rule:
# cat 70-disable_wol.rules
ACTION=="add", SUBSYSTEM=="net", KERNEL=="enp3s0", RUN+="/usr/bin/ethtool -s enp3s0 wol d"
Then rebooting the machine I checked the WOL setting and it really is disabled now:
# ethtool enp3s0 | grep Wake-on
Supports Wake-on: pumbg
Wake-on: d
# cat /sys/class/net/enp3s0/device/power/wakeup
disabled
So I then ensured that the battery was 100% charged and shut down the machine and left it two and a half days - rebooting this morning the battery was still at 100% charge and no longer discharges unnecessarily when the machine is switched off, so this is a clear indication of a bug in the BIOS for the WOL setting - it is still enabled despite the BIOS saying it is disabled!
How do I report this to Lenovo so that they can fix the BIOS and release a new one that is working?
I am aware of other users with different Thinkpads who seem to have the same problem, so this may be more widespread an issue than just on the S540.
It is also not just an issue with the battery running down when fully shut down but will likely also be a problem for a machine in suspend mode since the network interface may be consuming a watt or so of power when in suspend, which will again run the battery down at an unacceptable rate.
I cannot imagine any use case where it would be necessary to have WOL enabled on a laptop that is mostly going to be used mobile - so having the default setting to AC only enabled, and having a BIOS bug enabling it when it is explicitely disabled is a serious problem.

Anyone running windows in the same laptop can check the same issue of battery drain due to WOl being enabled by default - in the Device Manager under the network card, opening the settings menu for the ethernet wired card the default for Wake-on-LAN on my computer was set to enabled. This can be changed to disabled, and you may need to also disable the setting for Wake on Magic Packet. Also in the Power Management tab it is possible to uncheck the settings for "Allow this device to wake the computer" and "Only allow a magic packet to wake the computer"
In my laptop these were all set to enabled by default.

Tab bug in Pages − Some complex-script characters collapse all tabs on a line.

This problem is somewhat serious, since it basically turns tabs into spaces on any line that contains certain very common characters in Devanagari.
Basically, if you take the following text: "Hindi     हिन्दि     Hindi     हिन्दि" ...it will render in pages as: "Hindi हिन्दि Hindi हिन्दि"
However, taking this text: "Handa     हन्द     Handa     हन्द" will display completely as intended.
The culprit seems to be combining characters that move around inside a word -- in the above example, the Devanagari short "i" vowel ि (which appears on the left side of the letter it's modifying). Another character that triggers this problem is the top-curl "r" − for example: "artha     अर्थ     artha     अर्थ" renders as "artha अर्थ artha अर्थ"
This tab-collapsing happens immediately upon the appearance of the character on the line, and tab spacing is fully restored the moment the offending character is deleted. When "show invisibles" is turned on, the tab character is visible in all cases. Setting explicit tab-stops or changing text alignment has no effect.
This is a pretty serious error, as it effectively prevents any use of tabs in Hindi, Marathi, and Sanskrit text. I suspect it's more pervasive than this, considering the similarity of other indic scripts.
Is this a known issue? Can we expect a fix? I and other academics at my university already have to use Pages for all of our significant Devanagari work, given the lack of support in any other full-featured word processor on Mac OS. Having this ubiquitous formatting bug complicates things.

These are user to user help forums, and nobody can tell you if or when Apple will fix any particular problem. You need to report it to them using the feedback channel and/or bugreporter:
http://www.apple.com/feedback/pages.html
https://bugreport.apple.com
Other major word processors with Devanagari support include Nisus Writer and OpenOffice. I tried OO and it does not seem to have the tab problem. Also TextEdit of course, but it has fewer features.
PS I see this bug in 10.6 on my machine. Did you just now discover it, or do you think it was not present in some earlier version of Pages?

Safari Open Windows In New Tab Bug

In Safari when opening a window in a new tab by right clicking on a link. If you have a number of other tabs open to the right of the tab you are opening from then it will usually open the tab to the right of that tab as you are opening a page from the same site. but this does not always happen so I would consider this a bug. It used to be that it always opened it as the last tab which I think works best as you alwys know that it will work like that. The current implementation is just confusing in its inconsistencies.

In the article you linked to it says "But in Safari 5.1, opening a link in a new tab causes it materialize directly to the right of your current tab."
Which is of course the same as Chrome. However in Safari 5.1 it does not always do this, only sometimes and therefore I would call this a bug.

Middle Button Open in New Tab Bug

Like many people, I use the middle button when clicking links to open them in a new tab. In Safari 4.0.1 this feature is buggy. Sometimes it opens a new tab, other times it opens a new tab and the current tab ALSO switches to the clicked link. So you end up with two tabs of the same link. Seemingly at random it will work properly, and then not work.
Note* In order to eliminate the possibility of mouse malfunction, I tested it with firefox and camino. Both opened new tabs 100% of the time with middle clicks of my Logitech G5. Safari opened new tabs without also switching the current tab to the link only around 40% of the time.

''''' "Sometimes the button does not register with Firefox. And sometimes FF acts like I pressed it several times." '''''
Sounds like a mouse on its' way to mouse-heaven. Seriously, the exact symptoms I have seen with a dozen 3 button mouse's (?meese - ?mice) over the last 15 years. <br />
Not registering a click is usually due to a dirty contact. And the "double-click" is when the flat spring looses tension and bounces.
I have had similar happen with the left button, too. But when it happens to that button it is more noticeable much sooner.
I bought a box of a dozen A4D house branded infrared wireless 3-button mouse's for like $24.00 back in 2000 that were on clearance because the driver disk didn't support W2K, only Win95, 98, and NT4. I got newer drivers from the A4D website and wore all 12 out over the 8 or 9 years. I even fixed a few that broke from the parts from other broken mouse's. I still have 6 or 7 of them laying in the "needs to be fixed" box under my workbench. I'll probably never fix them though, the nano receiver USB mouses I have been using for the 4 or 5 years have much better battery life and lately only need one AA battery.

Possible code bug causing crash on Wine/Linux

As I am running Linux, I don't expect support as such but thought I would offer a possible contribution to the beta program as follows:
When starting Safari under Wine (an implementation of the Win32 API) on Linux, I get the following debug message:
DIB_GetBitmapInfo (44): unknown/wrong size for header
What I understand this to mean is that the Windows function GetBitmapInfo is being passed a dodgy parameter.
This is followed by a crash for me, but I guess on Windows, is quietly ignored.
I have seen a report on CodeProject regarding an identical crash caused by a coder setting the biSize member of the bmiHeader (BITMAPHEADERINFO) element of a BITMAPINFO structure to the incorrect size. In the example given, it had been set to sizeof(BITMAPINFO) rather than sizeof(BITMAPINFOHEADER)
e.g.
bmpInfo.bmiHeader.biSize = sizeof (BITMAPINFO);
instead of
bmpInfo.bmiHeader.biSize = sizeof (BITMAPINFOHEADER);
For any devs. interested as to whether there may be a bug, the call stack generated by Wine, showing the offsets from the base address of coregraphics.dll (loaded at 0x6b000000) is as follows, with the crash actaully occurring at '=> 1'
Backtrace:
=>1 0x6b262e97 in coregraphics (+0x262e97) (0x0033ed38)
2 0x6b0f9da4 in coregraphics (+0xf9da4) (0x0033f31c)
3 0x6b1e0fff in coregraphics (+0x1e0fff) (0x0033f4bc)
4 0x6b1d19ee in coregraphics (+0x1d19ee) (0x0033f578)
As I say, I'm not expecting any feedback on this - I'm just being neighbourly I also fully accept that I may be completely wrong in my assessment of the issue.
Dell Inspiron Other OS

There was an even earlier build than the two mentioned.
Talk about "early revisions" I guess so, and it doesn't look like there will be a unified version tomorrow.
I recall AYM had a note about video performance and in that instance, the build on the DVD was never than what was on the hard drive and within a week or so disk drives carried the "new, improved" video on disk as well.
There may be other changes that go hand-in-hand other than build, too. Did they look at the Boot ROM and SMC Version of the systems?
Boot ROM Version: MP11.005C.B00
SMC Version: 1.7f6

Foreach syntax + generics, Possible compiler bug?

I'm encountering an odd problem trying to use generics and the foreach (colon) syntax. The code in question:
for (Iterator<String> it = col.getParameterNames().iterator(); it.hasNext();) {}
for (String paramName : col.getParameterNames()) {}col is an instance of an inner class of the class whose method this code snippet is from, getParameterNames has the signature:
public Set<String> getParameterNames();
The first line, using the Iterator<String> explicitly, compiles fine. The second line, when present, raises the compiler error:
found : java.lang.Object
required: java.lang.String
for (String paramName : col.getParameterNames()) {
I cannot seem to reliably reproduce this situation in other (simpler) classes I write, but this one in particular seems to trigger it. Is it possible this is a compiler bug, or might there be something I'm doing incorrectly that I'm missing? Are my expectations about how the second line should work incorrect? It seems to in other circumstances...
javac is 1.6.0_01. Any ideas?

Here is a quick update, I'm more inclined to think of this as bad behavior now.
This code compiles:
public class Test {
Vector<InnerTest> inners = new Vector<InnerTest>();
    public class InnerTest {
       public Set<String> someSet() { return (new HashMap<String,String>()).keySet(); }
    public Test() {
        for (InnerTest it : inners) {
            for (String s : it.someSet()) {
}however, the following does not:
public class Test {
Vector<InnerTest> inners = new Vector<InnerTest>();
    public class InnerTest<P> {
       public Set<String> someSet() { return (new HashMap<String,String>()).keySet(); }
    public Test() {
        for (InnerTest it : inners) {
            for (String s : it.someSet()) {
}Again, the problem might be with my expectations (I haven't gone through the specifications yet with this in mind), but I can't fathom how or why the unused parameter would make a difference in that method's tpye matching.

Switch to tab Bug?

There seems to be a bug in the switch to tab logic where it will force-autocomplete an 'h' for http. This happens if you try to type an address and there's another tab whose address starts with the same letter.
An example probably explains best: let's say you already have a tab open to macnn.com. If you try to go to market.android.com by typing m-a-r etc., the address bar will automatically change to "Switch to tab: http://www.macnn.com" with the 'h' not selected. So if you keep typing it will go to harket.android.com. The only workaround is to keep typing and go back and fix it.
I can post a screenshot if there's a way to do that.

Exactly the same. My workaround is to type a space before the 'm'. Also, it doesn't happen for any other first letter - only 'm' causes the "Switch to tab:" to appear, even if I do have a dozen other weirdly-named tabs open.
'''I found a workaround''': check if your preference '''browser.urlbar.autoFill''' isn't set to '''true'''. Mine was, and these features apparently don't get along well. I set it to '''false''' and can now type 'm'-starting addresses.

Possible Keyword Bug

Okay,
I think I have found a possible bug with keywords, or maybe just an incositancy. It's kind of a messy situation so I'm hoping someone can help me out or maybe point me in the right direction to send this feedback to Apple.
I had a bunch of jpeg files from my older cameras that had already been tagged with keywords (in the IPTC keyword field I believe). Once I imported all of these into Aperture I stripped the keywords from all the images. That worked fine.
Before I get into the actual issue let me give a little bit of information on my Aperture library layout: I have folders created by year, then 1 project per month. So I have something like this:
2002
01 Janurary
02 Feburary
2003
01 Janurary
What's weird is if I create a new smart album at the folder level, the keywords listed in the search box are appropriate (only those actually added to images). However if I click on Library and create a new smart album (so that it searches the whole library) it lists all of my current keywords, plus all of those that I had removed (from the original files).
Anyone else run across this? Anyone know how to fix it? It's just a minor inconvience, but it does make it a bit of a pain to have a whole ton of keywords to select from in the search box (most of them no longer having any images associated with them).
Also I have searched for images that match the old keywords and it doesn't find any.
Thanks,
Mark

She suggests..
"Go to Window > Show Keywords HUD, and see if they are there. If so, you should be able to delete them from there."
Hopefully, they will then disappear from the Library list.
if not, it does seem like a bug.
Message was edited by: notorious

Tab Set not showing for Parent Tab - Bug?

Greetings,
(I figured someone else has experienced this issue, but after searching with multiple words I haven't found a thread.)
Using Application Express 4.0.2.00.07. The application in question is using Theme 7 - Modern Blue
My APEX application has over 20 pages and a lot of tabs, so I decided to create 2 new parent tabs (for a total of 3 parent tabs) and then assign the tabs to different tab sets so that I won't run out of horizontal space for all the tabs.
As best that I can tell everything with the parent tabs is set up correctly. I even had another developer look over everything I set up. The two newly created 2 parent tabs don't show their tab set of tabs when I click them. The parent tab that was first created still works, but not the 2 new ones. When we maintain everything via the tab interface everything looks OK, but when we look at the pages they are still assigned to the original tab and I don't see a way to change the tab set on the page level. We copied and deleted a page and when we did the page and its tab displays with the correct parent tab.
Is this a bug? It seems to be. It seems that creating the parent tab does not cascade down to the page level.
Also, regardless if it is a bug, is there a way to change the tab set at the page level? I hate to copy a lot of pages and delete the orignal pages, but maybe that's the only work around.
Also, maybe this is a theme issue? I know that some themes don't handle certain aspects correctly.
Thanks, Tony

I think I figured it out. There is a section on the page where you can change the Tab Set. It is under Display Attributes.

How It Was Fixed (Possible Software Bug Not Hardware): Getting the iMac Screen/Menus Garbled and/or Yellow Circle Before Getting Into Finder Issues?

Hi. Possible fix done to my late- 2009 iMac's screen/graphics issue that may work God willing, hopefully for most [In my case it sometimes had that yellow circle that appears before it goes to the Finder but mostly it was a messed up desktop and menus (unreadable mostly) after months, prayers and weeks of fixing it; recommended to be read entirely first coz' it's a bit complicated (like a lot of subplots). If uncomfortable to try coz' it involved a GPU stress test, contact your authorized Apple service center for their advice]. I had an iMac (late 2009) screen garbling a few hours ago (was weeks ago when it resurfaced until it got worse that it's at every boot on Mavericks):
† I booted to Snow Leopard USB external (my back-up OS) drive then run the first person shooter at redeclipse.net. I set everything to max, including the display, resolution and graphics setting with fullscreen and v-sync on. I then refreshed it which brought it back to normal (I then tested it's stability with GPUTest 0.7 with Furmark for 15 minutes). * if the display options have been set to max before, bring it back to the default then refresh and then max it again Possibly any games that's has the graphic settings (or more advanced) of Red Eclipse could work (other free ones are Xonotic and Open Arena which are based on Quake 1 or 3s engine I believe).
Optional but not recommended (have warrantied if that's still available or have it repaired at authorized service centers):
If that doesn't work, review articles and videos on how to open an Intel iMac and get an iPhone/iPad/another way to get to the 'net ready for research (I opened mine very carefully on the right side with a cutter with blade extended far prying it carefully then I inserted a flat end, sturdy plastic used for mixing epoxy then removed the cutter carefully to let the plastic mixing tool do the prying) to see if the cable connected to the logicboard which is on top of, is connected (mine was detached but I'm not sure if the adjusting and tilting of the screen overtime for 2 & 1/2 years, detached it) then do † above again.
It could to be a software problem, a possible Apple ATI driver bug that takes overtime to surface (2 1/2 years it resurfaced because this started in my case after upgrading to Lion when Apple coded things mostly from the ground up. Snow Leopard didn't have this problem).
Thank you for your time. Have a great upcoming sunday mass/great upcoming weekend. I hope this helps.
God bless, Rev. 21:4, Matt. 16:18

Does an external display also act in a similar manner as the internal one?
Some earlier Intel-based iMacs had graphic processor card issues; not sure what
the symptoms of the majority of them were, but some had odd patterns, others
went black, and some would range from OK to totally unusable. Among others.
So there is a chance the graphic processor may be going out; or just the circuitry
that controls the backlight. An inverter may be weak or other circuit to the display
could be wearing out.
http://www.apple.com/retail/geniusbar/
If you have access to an Apple Store with Genius bar, they can perform some kinds
of diagnostic tests there even though the computer is out-of-warranty; that may be
of help to narrow down the cause of the symptoms you've noticed. They may not be
able to repair it, however, at an Apple Store; as it is rather old by today's standard.
An Apple Authorized Service Provider could do repairs and testing on older models
the Apple Store's Genius and other may not be set up to handle due to vintage.
Find an Apple Authorized Service Provider
Visit an Apple Retail Store
There is a country locator page to help find either of the above in regions outside
of the US & Canada, not sure how the above links would work; and it appears my
bookmarks to the country locator page may not be accessible now to post here.
You may be able to get an idea about what kinds of parts support the display
function by name by looking into an iFixit.com repair guide for your iMac series.
Hopefully the parts supporting the display are the reason it is dimming down, as
a graphic processor failure likely would exhibit other behaviors than just dimming.
PS: I see you've added content to your thread after I'd started working on this
& the answer likely is a hardware repair; professional testing is worth the time
and you seem to have at least one other thread on the same topic....
Good luck & happy computing!
edited 2x

Possible "unlock" bug

Greetings.
I decided to post this here, as I dont have developer access for bugreporting site.
Using "The new iPad 3" with latest iOS 7.1.2
I found a strange bug by accident. I can repeat it, although it doesn't always work out.
Here it goes: When I turn my iPad on from black screen to start screen and slide unlock
bar like this (Finnish language set)
If I stop there (correct spot changes and not always the same) and then flip iPad, so
screen turns automatically (up and side both works).
This will result so, that unlock bar is stuck and I can't open iPad anymore. Not without turning
power off and then back on. This problem came with 7.0+
Would be intresting to know, if this is known thing and can others repeat this with other
iPads?
Thanks for your time.

I would suggest getting a copy of wireshark and see if the browser is behaving, I have seen
lots of issues where the server is closing the connection and Safari still tries to send more data, which
violates the RFC. You would also notice lots of tcp connections being opened possibly as well if the
site finishes loading. I have been trying to use Safari exclusively for a while, but somehow I always end up in Firefox. Hopefully they will have most of the gotcha's under wraps soon, but until than their is always
Firefox.

Possible Liquid Bug: Moving data into e-commerce layout

Liquid will not seemingly pass any data from outside an e-commerce layout into an e-commerce layouts is intentional or a bug.
If you create an include place it in a template then try to pass any data ie assign into any ecommerce layout it does not work.
If you need more help with reproducing this let me know.

What I have is a gloabal.inc this contains liquid that I would like to be used across a site ie url manipulations date manipulations and many many more. This is inside a head.inc placed at the very top of the template pages.
What this means is that the global.inc gets rendered first before anything else. You can then run liquid return results and then use it over and over with a simple {{myResult}} tag almost anywhere on a site. It works great, it is simple, fast to implement and has many applications. I can even create a library of .inc liquid files and can place their include's at will in global.inc and then access variables across a site to add and remove functionality. (Of course this is dependant on what you want to do and if it really needs to be global of course.)
I get that it is dependant on the way BC loads but if that is the reason then the ecommerce must render before the page template. Maybe it does, maybe there is another reason. If it is possible then it would be great to have working.
Is there other ways to get the result I want yes. But is it as simple, as fast and as easy to implement, add and remove no. If there is a better way I am all ears.

Aperture 2 - Possible UI bug?

G'day all,
I've been just being enjoying my first couple of days of Aperture 2. Fantastic, really enjoy using this version (keep it up Joe & team!)
I think I may have stumbled into a UI bug though. When I cycle through the viewer mode until the filmstrip disapears and the selected image is displayed at it's largest, I can't use the cursor keys or the arrows under the view to move to the next image.
Do you think it's a bug or is this intentional?
Cheers,
Dean
p.s. I'm looking for the Aperture feedbank link to send as feedback.

Is it a matter of what "window" has focus? (...which can be hard to tell) Try clicking the cursor once in the viewer then using the arrows? Does that work?
One way you can get into what you are seeing: If you click in a field in the metadata tab, then try and use the arrow key, its the metadata tab that is getting the keystroke, not the viewer, so the image doesn't change. You can see how it can happen, if you click there, the switch with a click to the adjustments tab, then adjust, then use the arrow key, you get nothing. If this is what you are seeing, then no need to quit the app, just click the window first with the cursor.

Command-Tab bug

Can anyone else reproduce this bug?
With no Finder windows open proceed to start Terminal.
Switch back to Finder via Command-Tab.
Try to create a new Finder window with Command-N.
Instead of a new Finder window I get a new Terminal window. Not what I wanted.

can't get the exact behaviour, but my Finder sometimes requires two presses of Apple N before a new window will appear. Also, sometimes even after launching the Terminal, focus is not given to Terminal, instead it remains with the Finder. Clicking on the Terminal window doesn't switch to Terminal, as expected. There is no way to get the focus to be the app in the foreground. I have to control click it in the dock and quit. note that it hasn't crashed (no force quit option), it simply refuses to focus.

Possible Tab Bug?

Similar Messages

Maybe you are looking for